feat(skills): add shipping-changes — change-shipping closed-loop skill - #30
Merged
Conversation
Distilled from the persona-architecture-v2 refactor (PR #29). A knowledge skill covering the end-to-end spine for non-trivial changes: research → proposal doc → phased guarded implementation → PR self-review → harden → merge. Core iron law: guarded commit chain (assert && test && verify && commit) so dirty changes never land. Complements automating-devops (the git/CI/release knowledge base); this is the process orchestration layer. Knowledge-only, Read-only. forge lint/scan clean; verify:skills 24->25; npm test 377 passed.
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.
What
New knowledge skill
shipping-changes— the orchestration spine for taking a non-trivial change from idea to merged PR.Distilled from a real session (the persona-architecture-v2 refactor, PR #29): research → proposal doc → phased guarded implementation → PR self-review → harden → merge.
Why a new skill (not folded into automating-devops)
automating-devopsis the knowledge reference for git/CI/testing/release.shipping-changesis the process spine that sequences a change end-to-end.automating-devopsas its knowledge base.Contents
assert && test && verify && commit && push) — never commit unverified changes; short-circuit blocks dirty stateVerification
forge lint✓ /forge scan✓ (knowledge skill, Read-only)npm run verify:skills: 24 → 25 skills ✓npm test: 377 passed ✓knowledge-only (
user-invocable: false,allowed-tools: Read) — no executable surface.