TheAstroByteTheAstroByte/astrobyte-agent-skills/skills/update-skill-stack/SKILL.md

update-skill-stack

Skill1 starsChanged 13 days agoMITView on GitHub

Review and apply upstream skill-stack updates without losing a personal profile or local skills. Use only when the user invokes $update-skill-stack or explicitly asks to update the adopted skill stack.

In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/adopt-skill-stack.mdcCursor rule
- adopt-skill-stackSkill
- api-and-interface-designSkill
- astrobyte-architectSkill
- astrobyte-git-identitySkill
- astrobyte-modeSkill
- astrobyte-project-startupSkill
- astrobyte-pr-workflowsSkill
- astrobyte-recallSkill
- astrobyte-reviewSkill
- astrobyte-show-workSkill
- astrobyte-tddSkill
- astrobyte-verify-projectSkill
- blast-radiusSkill
- browser-testing-with-devtoolsSkill
- ci-cd-and-automationSkill
- codebase-designSkill
- continual-improvement-checkSkill
- deprecation-and-migrationSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- frontend-designSkill
- frontend-ui-engineeringSkill
- git-workflow-and-versioningSkill
- grillingSkill
- handoffSkill
- hermetic-test-suitesSkill
- observability-and-instrumentationSkill
- performance-optimizationSkill
- pr-feedback-loopSkill
- prototypeSkill
- researchSkill
- security-and-hardeningSkill
- setup-astrobyte-skillsSkill
- shipping-and-launchSkill
- source-driven-developmentSkill
- technical-writingSkill
- to-questionnaireSkill
- typescript-best-practicesSkill
- unslopSkill
- writing-for-agentsSkill

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Check repository status. Stop for unresolved local changes that overlap the update.
line 12
Distinctive:
Create an isolated update branch or worktree.
line 14
Very specific:
After approval, push the update branch, open the pull request, wait for CI, merge, and run python3 scripts/install.py --operator <handle> …
line 20
Very specific:
Run python3 scripts/install.py --check and resolve drift, checkout differences, and shadowed routing.
line 21
Distinctive:
Follow the operator's update policy: manual only, notify, open a reviewed pull request, or merge and install automatically only when every …
line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Update the skill stack

Locate the adopted repository from the current checkout or ~/.config/astrobyte-agent-skills/install-manifest.json. Read config/repository.json, the active operator profile, docs/upstreams.md, and the installation manifest. When the recorded checkout is gone, python3 scripts/install.py --check from any checkout prints the clone and checkout commands that restore it; ask where to clone before running them.
Check repository status. Stop for unresolved local changes that overlap the update.
Fetch upstream and identify the current base version and available release. Do not merge yet.
Create an isolated update branch or worktree.
Compare upstream changes with personal profiles, custom skills, catalog composition, adapters, installer behavior, licenses, and migrations.
Show behavioral changes, conflicts, renamed or removed skills, source-pin changes, and any new scripts or external actions.
Preserve personal profiles and custom skills. A fully renamed skill set needs a manual mapping for each upstream change.
Apply the reviewed update. Run python3 scripts/validate.py and python3 -m unittest discover -s tests -v.
Present the diff and installation plan. Ask before pushing, opening or merging a pull request, or reinstalling.
After approval, push the update branch, open the pull request, wait for CI, merge, and run python3 scripts/install.py --operator <handle> from the merged checkout. Relay any routing approval it previews. An installation made before 0.5.0 needs --routing once.
Run python3 scripts/install.py --check and resolve drift, checkout differences, and shadowed routing. Then verify actual skill discovery in the selected agent products. docs/routing.md describes each check result.

Follow the operator's update policy: manual only, notify, open a reviewed pull request, or merge and install automatically only when every configured gate passes. Agent and repository permissions remain authoritative.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free