القائمة
Check tmp/RETRO.md before PR or human review so unresolved retro items do not slip through rawsql-ts developer workflow.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Assess and dispatch rawsql-ts developer tasks by tracing repository impact, concept and package boundaries, verification cost, difficulty, risk, model and reasoning effort, and Codex worktree requirements. Use when a new rawsql-ts issue, bug, feature, refactor, investigation, CI failure, review request, migration, or documentation change must be analyzed before action or handed to a new Codex task.
Report per-item attainment for completed rawsql-ts developer work.
Review tracked rawsql-ts package-level Scope, Test Policy, Authority Model, Technology Policy, review-plan, and generated review views before package implementation or documentation changes. Use only when those package-owned artifacts exist in the checked-out base.
Prepare rawsql-ts pull requests with the repository PR template and local readiness gate so required merge, CLI migration, and scaffold proof sections are not missed.
Capture meaningful recognition mismatches, false completion claims, and verification misses into tmp/RETRO.md for rawsql-ts developer work.
Run two-cycle self-review and triage before presenting rawsql-ts developer work to a human reviewer or requester.
| name | developer-pre-pr-retro-gate |
| description | Check tmp/RETRO.md before PR or human review so unresolved retro items do not slip through rawsql-ts developer workflow. |
Use this skill after the consistency review when rawsql-ts developer work is about to be reported as complete or presented in a PR and you need to confirm that unresolved retro items are not being ignored before human-acceptance review.
tmp/RETRO.md before PR handoff.done, partial, or not done.open, resolved, and accepted defer gate states.tmp/RETRO.md if it exists.PR gate status.open item as a blocker for PR readiness.accepted defer, confirm that the remaining risk, owner, and follow-up path are explicit.accepted defer as equivalent to resolved.