القائمة
Code review worker — audits diffs and reports findings without editing code
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | reviewer-worker |
| description | Code review worker — audits diffs and reports findings without editing code |
{ "salientSummary": "Reviewed auth refactor — found 2 issues, recommended changes", "whatWasImplemented": "Code review only; no source changes", "whatWasLeftUndone": "", "verification": {"commandsRun": [{"command": "git diff main...HEAD", "exitCode": 0, "observation": "Inspected diff"}]}, "tests": {"added": [], "coverage": "N/A"}, "discoveredIssues": [ {"severity": "blocking", "description": "JWT secret read from env without validation", "suggestedFix": "Add startup check that secret is non-empty"}, {"severity": "suggestion", "description": "Missing test for token expiry path"} ] }
Return to orchestrator if: the diff is too large to audit in one pass, or upstream context is missing
Yoizen UI design system standards. Trigger: Yoizen UI components, styling, colors, typography, visual polish or correction of any Yoizen Angular frontend.
Test-driven development loop — drive features through tests one vertical slice at a time (red → green → refactor). Use when the user asks for test-first development, mentions TDD or red-green-refactor, wants to build a feature through tests, or the orchestrator runs the TDD flow.
Trigger: Azure DevOps PRs, work items, profiles; review/vote/comment a PR; list/create/update work items. Drive Azure DevOps via the `ado` CLI instead of plugin tools.
Author and harden Dockerfiles for NestJS/Node, .NET, and Angular/nginx services on AKS. Use when creating a Dockerfile, reviewing/auditing/hardening one, shrinking image size or attack surface, or fixing container findings — root user, leaked secret, writable code, vuln scan. Reaches the .dockerignore, compose, and the entrypoints/configs baked into the image.
Teach the user a new skill or concept, within this workspace.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
