بنقرة واحدة
dotnet-web-api-review
.NET API review: architecture, validation, auth, EF Core, jobs, deployment, tests.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
.NET API review: architecture, validation, auth, EF Core, jobs, deployment, tests.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Effect TS review: services, layers, errors, Schema, concurrency, resources, tests.
Hey API review: OpenAPI specs, generated clients, SDKs, auth, validation, CI.
Container build review: Dockerfiles, image size, layers, SBOM, CVEs, reproducibility.
Container runtime review: env, secrets, health checks, resources, volumes, shutdown.
Production readiness review: deploy, rollback, monitoring, capacity, backups, runbooks.
Evidence-first bugfix workflow by workflow mode.
| name | dotnet-web-api-review |
| description | .NET API review: architecture, validation, auth, EF Core, jobs, deployment, tests. |
Review API changes for proportional architecture, contract clarity, validation, security, data consistency, async behavior, observability, and test coverage.
For broad or materially risky pull requests, recommend focused additional review only when independent expertise is likely to improve the verdict. Judge this from concrete risk, novelty, blast radius, reversibility, and context size—not file count or category matching alone. Small and conventional changes should remain one pragmatic pass.
When additional reviewers add value, split only by independent material surfaces. Each returns concrete evidence-based findings; the main agent removes duplicates and false positives and owns the proportional final verdict.
Use this skill together with itsol-task-intake for ambiguous work, itsol-self-review before handoff, and focused security-* or infra-* skills when the change touches trust boundaries or deployment behavior.