القائمة
Review the current branch for correctness, security, architecture, and project conventions before opening a PR. Delegates to the code-reviewer agent and adds StatusPro-specific checks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Open a PR for the current feature branch — validate, self-review, simplify, organize commits, push, create the PR, wait for CI and review, then address feedback. Use when implementation is complete and ready for review.
Write pytest tests using AAA pattern, project naming convention, and helper-based assertions (unwrap_as, unwrap_data, unwrap_unset). Delegates to the test-writer agent.
Structured code review using 6 dimensions. Works with or without the code-reviewer agent.
Create conventional commits with quality gates and validation
Generate or update docstrings, ADRs, READMEs, cookbook recipes, and user guides. Knows about MCP help-resource drift and ADR numbering scheme.
Respond to PR review comments systematically in thread context
| name | code-review |
| description | Review the current branch for correctness, security, architecture, and project conventions before opening a PR. Delegates to the code-reviewer agent and adds StatusPro-specific checks. |
| allowed-tools | Read, Grep, Glob, Bash(git diff*), Bash(git log*), Bash(git show*), Bash(uv run poe check) |
Review current branch vs main for shippability — catch bugs, anti-patterns, and architecture violations before PR.
api/**/*.py, models/**/*.py, client.py must come from regeneration, never manual editsisinstance(_, type(UNSET)), hasattr on attrs fields, manual response.status_code == 200, or wrapping API calls with retries (resilience is at the transport layer)statuspro_mcp_server/.../resources/help.py must be updateduv run poe check must be green before approving; failures are BLOCKINGDelegate the 6-dimension review (correctness, design, readability, performance, testing, security) to the code-reviewer agent. Pass it the diff range:
git diff main...HEAD
api/, models/, client.py — if present, verify they came from uv run poe regenerate-client + uv run poe generate-pydanticuv run poe test-coverage ≥ 87% on coredocs/adr/uv run poe check
Any failure is BLOCKING.
Use code-reviewer output structure (BLOCKING / SUGGESTION / NITPICK with file:line references). Append the StatusPro-specific findings under their own subsection.
docs/statuspro-openapi.yaml is consistent (consider spawning spec-auditor); confirm both regenerate-client and generate-pydantic ran.LSP findReferences (or LSP incomingCalls) on the changed function to enumerate callers and confirm each still works with new semantics.code-reviewer agent — does the heavy lifting; this skill adds StatusPro contextpr-preparer agent — process readiness (commit format, coverage threshold, generated-file integrity)domain-advisor agent — answers "which pattern applies here?" questions during review