Repository navigation
skill(issue-shape): how to file an issue the shape gate keeps open (Closes #10060) - #10063
Merged
Merged
Conversation
…loses #10060) The issue-shape gate (specs/policy/issue_shape.t27, #7498) closed #10054 seconds after filing because the body lacked Boundary, User Scenarios and Requirements. Nothing in AGENTS.md or the skills told an agent about it. - .claude/skills/issue-shape/SKILL.md: reading guide to the spec (the spec wins): sections, Boundary path trap, checking a body with the generated check_issue() on the lab, recovery from shape-refused via gh issue edit. - specs/skills/t27-issue-shape.t27: skill card per specs/skills/README.md. - AGENTS.md section 3: a pointer next to the Issue gate item, no restated checks. Lab: t27c test-report specs/skills/t27-issue-shape.t27 -> 1 pass, 10 runtime asserts, exit 0; a wrong-ID copy fails (negative control). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
gHashTag
enabled auto-merge (squash)
October 17, 2026 17:56
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
1 participant
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 #10060
What
The issue-shape gate (
specs/policy/issue_shape.t27, #7498, workflowneeds-boundary.yml) closed #10054 seconds after filing because the body had no Boundary, User Scenarios or Requirements sections. Nothing in AGENTS.md or the skills mentioned the gate. This PR adds pointers to the spec, which stays the single source of truth:.claude/skills/issue-shape/SKILL.md: a reading guide to the spec, which wins wherever the two disagree. It covers:path :: fn NAMEregion form;check_issue()on the Railway lab before filing, using the harness copied from the workflow, with a negative control;shape-refusedwithgh issue edit --body-file; a passing edit makes the workflow reopen the issue and remove the label.specs/skills/t27-issue-shape.t27: the skill card, following thespecs/skills/README.mdschema.AGENTS.mdsection 3: one pointer line under the existing "Issue gate" item. It does not restate the checks.No gate logic changes.
Evidence (Railway lab, t27c release build)
Negative control: a copy that asserts
ID == "t27/wrong"reportsFAIL basic_constants.The new text is ASCII. The local pre-commit
own-languageandforeign-budgethooks pass: this PR adds only prose and a.t27file.Noticed, not changed
The header comment in
specs/policy/issue_shape.t27names the workflow.github/workflows/issue-shape.yml, but the file in the tree isneeds-boundary.yml. The skill says so; the spec comment is left for a separate change.🤖 Generated with Claude Code