القائمة
Rank open GitHub epics and issues by priority and recommend what to work on next. Read-only — never modifies issues. Invoke as /prioritize (optionally scoped to a label, milestone, or epic).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Resolve PR review comments for an in-review issue — fix them in the issue's worktree, re-run the gate + C as needed, push, and reply per thread. Fourth stage of the CQLite delivery pipeline. Use when the owner leaves PR comments and says "address
Turn a rough idea into one scoped, labeled GitHub issue (one P0–P3 + status:ready, testable acceptance criteria), and decide oracle-vs-design routing. First stage of the CQLite delivery pipeline. Use when the owner says "groom <idea>", "file an issue for X", or brings a rough idea to scope.
Implement an approved issue — spawn sstable-developer (TDD) in the issue's worktree, run rust-reviewer + roborev on the lite-green diff BEFORE any full gate (review-first is default), open the PR, then hand the endgame (the ONE full gate → C → final roborev → merge-on-green → finalize) to a disposable flow-closer agent so gate/review churn never accretes in the lead session. Third stage of the CQLite delivery pipeline. Requires owner approval of the spec (design-driven) first. Use when the owner says "implement
Pre-push validation checklist (cargo fmt, clippy with zero warnings, feature flag testing, test suite), CI monitoring, merge process, and release quality gates. Use when preparing to push code, validating changes before PR, running CI checks, merging PRs, or preparing releases.
Report status across all in-flight CQLite delivery work — render the shared GitHub Project claim board (item, status, assignee, priority) with drift + abandoned-claim reconciliation, then surface and drive the single furthest-along item waiting on the owner (a green PR to merge, a spec to approve), or offer a claim-aware pick-list. Use when the owner asks "where do things stand", "what's next", "unblock me", or "what needs me".
Activate a groomed design-driven issue — create its worktree + branch (1:1:1:1), run OpenSpec propose to produce proposal/design/specs/tasks, render the spec + recommended design INLINE, then STOP for the owner's approval. This is Seam 1; it never implements. Second stage of the CQLite delivery pipeline. Use when the owner says "activate
| name | prioritize |
| description | Rank open GitHub epics and issues by priority and recommend what to work on next. Read-only — never modifies issues. Invoke as /prioritize (optionally scoped to a label, milestone, or epic). |
| disable-model-invocation | true |
| argument-hint | ["optional label","milestone","or epic number"] |
Produce a prioritized view of the backlog. This skill is READ-ONLY — do not edit, comment on, assign, or close anything.
Use gh to list open work. If $ARGUMENTS names a label, milestone, or epic, scope to
it; otherwise cover all open issues.
gh issue list --state open --limit 200 --json number,title,labels,assignees,milestone,createdAt,updatedAtRate every issue on this rubric and show the factors, not just a number:
Output a ranked, skimmable table (rank, #, title, impact/effort, why) and a short "START NEXT" line — the single epic or issue you'd pick up now and why. Assume I may be reading this on my phone.