as-is-sync
Skill2 starsChanged 4 months agoMITView on GitHub
Regenerates the as-is map from the code and commits the result. Use after structural changes (new modules, endpoints, migrations) or when /as-is detects it is out of date.
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- as-is-learnSkill
- as-isSkill
- clarifySkill
- consistencySkill
- context-reportSkill
- convergeSkill
- harness-initSkill
- implement-taskSkill
- orchestrateSkill
- repo-addSkill
- repo-mapSkill
- spec-createSkill
- spec-reviewSkill
- system-mapSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
If everything is legitimate: commit chore(as-is): sync map with <commit> — <1-line summary>.
- Distinctive: line 19
If you detected architectural drift: commit the map anyway (the as-is ALWAYS tells the truth) but leave the finding recorded for the gate.
- Distinctive: line 20
ALWAYS tells the truth) but leave the finding recorded for the gate.
≈ “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.
Files
- Run
./scripts/generate-as-is.sh. - Review
git diff knowledge/as-is/and summarize IN ARCHITECTURE LANGUAGE what actually changed: new module, new dependency between domains, endpoint added/removed, schema migration. - CRITICAL VALIDATION — compare the changes against the rules:
- Does a new dependency violate service domain boundaries (rules/api-design.md) or any current ADR? → report it as architectural drift and ESCALATE to the Architecture gate. Do not normalize it by committing it silently.
- Did an endpoint appear without an OpenAPI contract? → flag it as debt.
- If everything is legitimate: commit
chore(as-is): sync map with <commit> — <1-line summary>. - If you detected architectural drift: commit the map anyway (the as-is ALWAYS tells the truth) but leave the finding recorded for the gate.
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.

