Convex-Dev/convex / .claude/skills/issue-triage
issue-triage
VerifiedTriage the open Convex issues against a fixed rubric — close what is done or superseded, give each a type label, and collect everything that needs a maintainer decision into one review sheet. Use when asked to review or triage all open issues.
Issue triage
Triage keeps the open issues to outstanding bugs and enhancements. Apply the same rubric on every pass so passes can be compared.
Rubric
- Close issues that are done or superseded:
--reason completedwhen done;--reason "not planned"plus theduplicatelabel when superseded. Add a one-line comment citing the evidence (file, CAD or PR). questionfor an unresolved question or ambiguous point. Post the question if the thread does not already state it.bugonly for an active defect that still needs fixing for the next release.performancewhere optimisation or efficiency matters.securitywhere security matters.enhancementfor a request beyond current functionality.
Each open issue carries exactly one type label: bug, enhancement or
question. performance and security are extras. For areas use the existing
labels (peer, convex-db, UCAN, operations); create no new ones. No open
issue ends unlabelled.
Fix an issue directly only if the fix is genuinely quick, adds no complexity,
needs no design decision and touches no network state, consensus or core code;
flag it for review. metadata.cvx is part of the genesis state
(Init.createBaseState), so even a docstring typo there is not a quick fix.
Procedure
- List the open issues:
gh issue list --repo Convex-Dev/convex --state open --limit 500 --json number,title,labels. - Fan verification out to read-only subagents by area, about 15 issues each, each writing its findings to a scratch file.
- Verify every status claim against the code before acting on it: a target
such as "v2" is stale while
Migrations.LIVE_VERSIONis still 0. Find the commits for an issue withgit log -P --grep='#NNN\b'; without-Pthe\bis ignored and#354also matches#3540. - Act directly only on labels and on closures verified as completed. Put not-planned closures, consolidations and every comment to an external contributor into one numbered review sheet for the maintainer.
- Report by action: closed, relabelled, commented, for review.
Never put exploit detail in a public comment: an edit keeps the original in the issue's history. Exploitable vulnerabilities follow SECURITY.md.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |