apply-wiki-change
Skill8 starsChanged 5 months agoMITView on GitHub
Use when the user has approved a Product Wiki proposal and the wiki needs to be updated before implementation.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- compile-changeSkill
- generate-checksSkill
- import-codebaseSkill
- propose-changeSkill
- reconcile-wikiSkill
- review-architectureSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 3 are distinctive, and 10 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.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
If a template is missing, do not infer wiki unit or overview structure from schemas, lints, previous examples, or memory.
- Distinctive: line 22
Stop only if the canonical contract cannot be restored.
- Distinctive: line 26
Read the approved proposal.
- Very specific: line 27
Read templates/wiki-unit-template.md, templates/wiki-overview-template.md, and references/wiki-write-rubric.md.
- Distinctive: line 31
create / update / link / supersede / none
- Very specific: line 34
Write or update the smallest possible set of files under wiki/, using templates/wiki-unit-template.md for new units.
- Very specific: line 35
Follow references/wiki-write-rubric.md for two-way linking, the product-language vs implementation-detail split, and the connectivity rule.
- Very specific: line 37
Keep the proposal status as approved.
- Very specific: line 38
Do not mark it implemented until compile-change has added executable checks and code.
- Very specific: line 41
Update related links in both directions when safe, keeping every unit connected per the connectivity rule in …
- Very specific: line 42
Update wiki/index.md if a new unit family or important entry needs discovery.
- Very specific: line 44
Update it when the change affects what the product is, who it serves, main journeys, main capabilities, important rules, boundaries, or key …
- Very specific: line 45
If the overview is still accurate, refresh its updated date and review notes.
≈ “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
Apply Wiki Change
Your job is to apply an approved proposal to the product wiki. This is the point where the wiki changes before code.
Preconditions
- Proposal exists under
intake/proposals/. - Proposal status is
approved, or the user explicitly approves it in the current conversation. - Application code is not edited during this skill.
templates/wiki-unit-template.mdexists and can be read.templates/wiki-overview-template.mdexists and can be read.
If a template is missing, do not infer wiki unit or overview structure from schemas, lints, previous examples, or memory.
First run node scripts/repair-contracts.mjs --write, then re-run node scripts/template-lint.mjs.
Continue if repair succeeds.
Stop only if the canonical contract cannot be restored.
Workflow
- Read the approved proposal.
- Read
templates/wiki-unit-template.md,templates/wiki-overview-template.md, andreferences/wiki-write-rubric.md. - Build a unit application table from the proposal:
- unit ID
- unit type
- create / update / link / supersede / none
- target file
- source section in the proposal
- Write or update the smallest possible set of files under
wiki/, usingtemplates/wiki-unit-template.mdfor new units. Followreferences/wiki-write-rubric.mdfor two-way linking, the product-language vs implementation-detail split, and the connectivity rule. - Apply acceptance criteria as first-class wiki units under
wiki/acceptance-criteria/, not only as bullets inside a story. - Keep the proposal status as
approved. Do not mark itimplementeduntilcompile-changehas added executable checks and code. - Preserve existing IDs. Do not rename IDs unless the proposal explicitly says so.
- For decisions, supersede old decisions instead of deleting or rewriting historical rationale.
- Update related links in both directions when safe, keeping every unit connected per the connectivity rule in
references/wiki-write-rubric.md. - Update
wiki/index.mdif a new unit family or important entry needs discovery. - Review
wiki/overview.md. Update it when the change affects what the product is, who it serves, main journeys, main capabilities, important rules, boundaries, or key decisions. If the overview is still accurate, refresh itsupdateddate and review notes. - Append a dated entry to
wiki/log.md. - Re-read the proposal and verify every proposed wiki change is represented or explicitly deferred.
- Run
node scripts/wiki-lint.mjs. - Run
node scripts/wiki-overview-lint.mjs. - Run
node scripts/wiki-link-lint.mjs. - Run
node scripts/proposal-lint.mjs. - Run
node scripts/proposal-traceability-lint.mjs. - Stop before implementation.
At this stage, approved acceptance criteria are pending compile.
They do not need manifest coverage yet.
The full node scripts/product-wiki-check.mjs gate should pass after compile-change has added check coverage, implemented code, and marked the proposal implemented.
Output
Return:
- Files changed.
- New or updated stable IDs.
- Proposal units applied / deferred.
- Whether
wiki/overview.mdchanged or was reviewed unchanged. - Any missing links or open decisions.
- Confirmation that wiki and proposal lints passed, or the exact failures.
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.

