extract

Files (3)

• SKILL.md
• wiki-lint.mjs · scripts/
• wiki-lint.test.mjs · scripts/

SKILL.md (first lines)

# Extract

Future blueprints look up the wiki for decisions they don't have to research again. Read `schema.md` in the knowledge root first (path from the session nudge). It owns the layers, the page rules, the index and log formats; `_TEMPLATE.md` owns the page shape. Follow them exactly.

## Harvest

From the blueprint, in order of value:
1. Inputs that corrected direction (user feedback), kept verbatim.
2. Decisions sourced from `user:` or `research:`.
3. Findings in `<name>.runs/inspect.md` that led to a fix.
4. Approaches that failed, with the reason.
5. The command that builds and runs the project's tests, when the repo's wiki pages lack it.

Skip decisions sourced from `data:`; the code already says them.

## Keep or drop

Apply the schema's bar for what earns a rule. Open the cited code before promoting a claim. When a claim contradicts an existing rule, the newer, better-cited one wins and the old rule gets `superseded by` it.

## Write

1. Copy the source verbatim into `raw/<org>/<repo>/<date>-<topic>.md` with secrets redacted.
2. Edit the page that already owns the topic. Sharpen or delete the old rule before adding a new one. A page at the schema's size ceiling gets split by trigger, not extended.
3. Update the scope `index.md`, the wiki `index.md` for a new scope or pattern, and `wiki/log.md`. Move the oldest log lines to `wiki/log/archive.md` before the log reaches 100 lines.
4. Set `LastVerified` to today only on pages whose cited code you opened.

## Verify

Run the wiki lint tool from the nudge on the scope directory you worked in, `index.md` and `log.md`, with wiki-relative paths and the repo checkout. Add each pattern page you changed:

```bash
node <wiki lint tool> <knowledge root> orgs/<org>/<repo> index.md log.md --repo <repo>
```

Fix every violation in the files you changed. A `cite` error means the cited code moved or is gone: update the line when the rule still holds, otherwise mark the rule `Status: stale` or `superseded by <rule>`. Pages you left alone may carry older violations: report their count and leave them.

## Close

Append ` | Extracted: <YYYY-MM-DD>` to the blueprint's `Repo:` line, then run the blueprint tool's `check` on it.

## Lint

When asked to lint, run the tool on the requested scope, or without paths for the whole wiki, and report the `byRule` counts and errors. The tool can't see whether cited code still supports its rule, contradictions between pages or duplicate guidance; check those by opening the cited code and comparing pages. Repair only when asked.

## Return

Report the candidates considered, the pages changed, the claims marked stale or superseded, the lint result, and the blueprint's `check` status.

From abossard/virtucon, MIT.

More from abossard/virtucon