Repository navigation
Let the dogfood skill carry a supported fix through release - #152
Merged
Merged
Conversation
The dogfood skill was read-only unless the owner asked for a change. When the evidence supports a fix, it now carries that fix through implementation, verification, and a new plugin release without a separate request. Explicit analysis-only, planning-only, and no-release restrictions still bind, and it still stops at a real product choice or an action outside its authority. This is contributor tooling outside the installable package, so VERSION stays. 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
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.
The contributor
dogfoodskill was read-only unless the owner asked for a change. Its closing paragraph now says that when the evidence supports a fix, the skill carries it through implementation, verification, and a new plugin release for users without a separate owner request.The limits stay the same. Explicit analysis-only, planning-only, and no-release restrictions bind. The skill stops at a real product choice or an action outside the authority granted for the workflow. Its "Design the fix" section still allows a change only when the evidence names a defect in the package's wording. Nothing else in the skill or the repository described it as read-only.
The skill is contributor tooling outside
plugins/skiphow/, so there is no version bump. Local evidence:tests/test_package.pypassed (13 tests, including the dogfood skill's shared-path test) andgit diff --checkwas clean. The full gate runs in this PR's CI.🤖 Generated with Claude Code