docs(skills): require full-scope completeness bar in gardening-generated issues#8156
Merged
Merged
Conversation
…ted issues Contributors' AI-harness agents read only the issue text and default to the least-effort interpretation that could plausibly close a checklist. Add an explicit completeness bar to the contributor-pipeline-gardening skill: every Requirement must be concrete/testable, every Deliverables item ships together in one PR (no partial credit for a subset), and Expected Outcome must be a falsifiable end-state checkable from the PR diff alone.
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
|
2 tasks
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.
Summary
.claude/skills/contributor-pipeline-gardening/) generates most of this repo'sgittensor:*contributor-available issues. Contributors' AI-harness agents read only the issue text and take the least-effort path unless the text closes off ambiguity.SKILL.md, and adds a fixed "ships together" line to the issue body template inreference.md.Doc-only change under
.claude/skills/**; no code/schema/route changes.Test plan