Repository navigation
D220 — an update generates the skills again from its playbooks - #398
Merged
Merged
Conversation
The skills are generated from the playbooks and git-ignored. An update that moved a playbook left them behind, and the first nstack attest failed Fitness on S3. Where the person generated skills (.claude/skills/), nstack update now generates them again and says so; what stops it is said with its action. Agent-Session: nstack-os-d220 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
napkinstack-admin
approved these changes
Nov 14, 2026
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.
Why
A downstream project took v0.29.0. Right after
nstack update, its firstnstack attestfailed Fitness on[S3] skill 'verification' out of sync with .nstack/playbooks/verification.md. The update moved the playbook, and the skills, generated and git-ignored, stayed as they were. Neither the update's output nor its next step said to runnstack skills.What
nstack update: where the person generated skills (.claude/skills/), it generates them again from the updated playbooks, on the update's branch, and says so. They are derived and git-ignored files, so nothing of anyone's is lost. What stops it is said with its action. An update stopped on conflicts saysnstack skillsin its action. Market: a package manager's post-install step regenerates what it derives.nstack skills: removes a generated skill whose playbook is gone (still loaded by the agent, said by no rule), but never a skill a person wrote, which has no banner.Checks
run.sh(skills generated at v90.1.0, a playbook moved by v90.2.0,nstack skills --checkafter the update) and the orphan's test.uv run bash platform/tests/run.sh: 1303 passed.nstack fitness: compliant.Register row D220.
🤖 Generated with Claude Code