srs-upgrade
Skill0 starsChanged 33 days agoMITView on GitHub
Upgrade the SRS-DD framework installed in this project — the checker, the viewer, the gate, the skills and, on request, the agent guides. Invoke when the user asks to update or upgrade SRS-DD, to pick up a new framework version, or when the checker reports a version older than the one they expect. Runs srs-dd/tools/srs_upgrade.py, which fetches the framework this project was installed from.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- skeleton/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skeleton/CLAUDE.mdCLAUDE.md
- srs-arch-auditSkill
- srs-arch-harvestSkill
- srs-archSkill
- srs-auditSkill
- srs-baselineSkill
- srs-betSkill
- srs-buildSkill
- srs-checkSkill
- srs-commitSkill
- srs-harvestSkill
- srs-initSkill
- srs-newSkill
- srs-pageSkill
- srs-releaseSkill
- srs-reviewSkill
- srsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Run it without arguments:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
<!-- Copyright (c) 2026 CRELLIA S.L. — part of SRS-DD, distributed under the MIT License -->Upgrading the framework in this project
Everything needed is already here: srs-dd/tools/srs_upgrade.py fetches the framework this project was installed from, runs its installer against this repository, and removes what it fetched.
There is no clone to keep around and no address to look up.
Procedure
Show the change first. Run it without arguments:
python3 srs-dd/tools/srs_upgrade.pyIt prints the version transition, the upgrade notes for the versions being crossed, and the exact created / refreshed / moved / skipped list — then asks. Nothing has been written at that point.
- Read the upgrade notes to the user, not just the file list.
They are the only place that says what a new version expects of this project.
Where a note calls for an action here, say so plainly.
The identifiers in a note are the framework's, not this project's: relay them as written, never through
--cite, which would find this project's requirement under the same number. Apply on their word. In a terminal, answer the prompt. Without one — an agent session, a script — pass
--yes, and only after the user has seen step 1:python3 srs-dd/tools/srs_upgrade.py --yes- Commit the result together with the regenerated
specs/90-traceability.md: the refreshed checker may write a matrix that differs from the committed one, and the CI gate compares it.
What it does and does not touch
Rewritten whole: srs-dd/ — the tools, the standard (srs-dd/standard.md) and those of the layers, the method's articles, the framework's guide — and the skills under .claude/skills/srs-*; and, inside AGENTS.md, only the region between <!-- srs-dd --> and <!-- /srs-dd -->.
Left alone: everything else — AGENTS.md outside the region, CLAUDE.md, .gitattributes, the pre-commit hook, the pipelines, specs/constitution.md. They are the project's files; what they hold of the framework is a call to srs-dd/tools/srs_gate.py or the region.
A project installed before 0.22.0 is moved into the directory: the tools and the standards leave tools/, specs/, grounds/ and arch/, and the report says what the hook, the pipelines and the guide now have to call.
The specification is never touched. Requirements are the project's own.
Wiring the gate
The hook and the pipelines are this project's files, never rewritten by an upgrade, and the installer's report — Pre-commit gate, Pipeline gate — says whether git runs a hook, whether that hook calls srs-dd/tools/srs_gate.py, whether any pipeline does, and prints what to add where not.
Read it after every run and add what it prints where the project runs its hooks: a line in a hook of the project's own, a repo: local hook in .pre-commit-config.yaml, the line in .husky/pre-commit, a command in lefthook.yml — with pre-commit install or lefthook install where git runs nothing yet — and a step in a workflow under .github/workflows/ or a job in .gitlab-ci.yml.
Where nothing runs at all, git config core.hooksPath .githooks switches the starter on, and only then: the switch turns off whatever ran before.
On a service the installer does not know, read its pipeline and add the step in that service's form.
Done is the report, run again, saying the hook and a pipeline call the gate — or your reading of the step on a service it does not know; a hook git does not run is a gate that looks installed.
Where the region landed
The installer finds the framework's region of AGENTS.md by its border alone: a line holding nothing but a marker is one, a sentence naming the markers is not, and a fenced example of those lines reads to it exactly like the region.
So open the file once and see that the region stands where an agent meets the method's rules — not inside an example or a fenced block.
Where it landed wrong, move the two marker lines to where the rules belong and run again.
Options worth knowing
--ref v1.2.0— fetch a specific release instead of the default branch, for a project that pins its framework version.--from ../srs-dd— use a clone already on disk; nothing goes over the network.
When it refuses
Exit code 2 means nothing was written: no specs/ beside tools/, the framework repository itself, --ref given with --from, a --from path that is no framework clone, no git, an unreachable address, or no terminal to confirm at and no --yes. Any other code is the installer's own — 1 where the project's checker rejects the result.
Exit 3 means the installer rolled back and the project is untouched.
Both are safe to retry once the cause is fixed.
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
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.

