Repository navigation
Add a /triage skill for sorting new project items - #184
Merged
Merged
Conversation
The skill collects the issues in the project's Triage column (or given issues), checks each against develop, proposes Priority, Phase, Seq, Plan, Size, labels and milestone in one table and writes the fields only after the maintainer approves. It also records how an agent triages an issue it opens at the maintainer's request. CLAUDE.md lists the skill and GITHUB-SETUP mentions it in Intake. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #177
What
.claude/skills/triage/SKILL.md:/triage [issue ...]collects the issues in the project's Triage column (or the given issues), checks each againstdevelop(still true, moved, duplicate, blocked, against an ADR), proposes Priority, Phase, Seq, Plan, Size, labels, milestone and Status in one table, asks the maintainer, and writes only the approved values. Guardrails: nevermaintainer-only; no closing, comments or body edits without approval;Readyonly when the maintainer says so.Ready(orIn progressif a PR moved it), and a milestone only when the request names the release.CLAUDE.md: the skill in "Skills and agents"; "Issues and the project" points to it for the Ready decision and for sorting follow-ups.docs/GITHUB-SETUP.md: Intake mentions/triage; the Plan field mentionsF<n>follow-up ids.Differences from the issue text (maintainer decisions)
Readywhen the maintainer says so in the approval, and an issue opened at the maintainer's request is setReadydirectly.Dry run (steps 1–3, no writes)
The Triage column is empty (0 items), so the dry run replayed the five issues sorted by hand on 2026-10-30 (
/triage 159 160 162 168 176):skip-changelog,provider:nbpci,area:repoenhancement,area:httpNotes: #159 and #162 are closed (fixed by #181 and #180) and were skipped as step 1 says. #160, #168 and #176 were checked against
develop(NbpTableEnumValidatorused only by its test;format-cs.sh:8and:11unchanged; no display path inRestRequestExecutor), with no duplicates or blockers. The run predates the rule that an already-triaged issue keeps its Seq and Plan; with it, these three keep 435/F4, 436/F5 and 560/F6. Its other findings (item id lookup, trimmedgh issue view, Seq fallback, Git Bash path conversion, milestone issue list) are fixed in the skill, and every changed command was re-run.Checks
F<n>= F8, field ids, labels, milestones, issue view); the write flags (item-edit --date/--number/--text,item-add --url) checked with--help.git diff --check: clean. No code changes, so no build or tests.revieweragent: no blocking findings; its milestone guard and the wording points are applied..claude/settings.jsonneeds no change: the read-only calls are already allowed, the writes keep prompting.🤖 Generated with Claude Code