migration_audit
Skill2 starsChanged 3 months agoMITView on GitHub
Deterministically verify that a framework, protocol, dependency, or build migration actually removed legacy paths and markers before VALIDATOR runs. Returns PASS, FAIL, or UNCERTAIN with bounded path-only evidence; never executes project code.
In this repository75 other files it gives its agents.
- AGENTS.mdAGENTS.md
- clean-cacheSkill
- agent-cacheSkill
- app_testSkill
- asset-qualitySkill
- auto_distillSkill
- auto-memorySkill
- auto_routerSkill
- benchSkill
- bootstrapSkill
- botte-proxySkill
- cacheSkill
- capabilitiesSkill
- cardinalSkill
- cavemanSkill
- checkupSkill
- clarificationSkill
- clusterSkill
- code_fingerprintSkill
- completion_proofSkill
- conductorSkill
- context_budgetSkill
- context_profilerSkill
- context_slicerSkill
- context_windowsSkill
- control_loopSkill
- cost_estimatorSkill
- cwe_kbSkill
- dag_optimizerSkill
- dashboardSkill
- decision-ladderSkill
- demoSkill
- diff_languageSkill
- directives_auditSkill
- docgenSkill
- docs_stewardSkill
- eventsSkill
- fallow_likeSkill
- fast_contextSkill
- fixSkill
- harness_deltaSkill
- hermes-bridgeSkill
- hf_provenanceSkill
- infra_advisorSkill
- ingestSkill
- llm_backendsSkill
- llm_mcpSkill
- loaderSkill
- mcp_gatewaySkill
- meta_harnessSkill
- metricsSkill
- monte_cristoSkill
- mousquetairesSkill
- nlp_deterministicSkill
- nn_auditSkill
- prefix-prunerSkill
- prefix_treeSkill
- preflightSkill
- prompt_improverSkill
- reportSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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 8
Use this stage after BUILDER and before VALIDATOR:
≈ “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
Migration Audit
Use this stage after BUILDER and before VALIDATOR:
... -> BUILDER -> MIGRATION_AUDIT -> VALIDATOR -> ...Create .botte/migration-audit.json using
botte.migration-audit-spec/v1, then run:
botte migration-audit --project . --jsonSupported checks are text_absent, text_present, path_absent,
path_present, and paths_not_both. Text is matched literally, not as a
regular expression. The report never contains matched source text or absolute
paths. An incomplete scan returns UNCERTAIN; a normal test pass cannot
override a migration-audit failure.
The stage is deterministic, stdlib-only, SIMULATE/SHADOW, and cannot grant
ACT, modify the audited project, or execute its code.
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.