ADR Wiki

Architecture Decision Records live on the forge wiki and are cloned into docs/adr/ during setup.

Wiki URL

<wiki-url>

Derived from the forge remote during /setup-skills.

On first setup, /setup-skills clones the wiki:

git clone <wiki-url> docs/adr/

And adds docs/adr/ to .gitignore.

On subsequent sessions, pull the latest:

cd docs/adr/ && git pull --rebase

Authentication for pushing ADR changes uses: <auth-method>

Forge CLI token — gh or tea already stores credentials; use them for git push via HTTPS with token auth.
SSH key — wiki remote uses git@<host>:<owner>/<repo>.wiki.git.
Dedicated token — stored in env var GIT_WIKI_TOKEN; used as password in HTTPS URL.

At end of every session, the agent:

cd docs/adr/ && git add -A && git commit -m "docs(adr): <action> ADR-NNNN — <description>"
git pull --rebase (handle any web UI edits)
git push

If a conflict arises during rebase, surface it to the user for resolution.

docs(adr): add ADR-NNNN — title
docs(adr): update ADR-NNNN — reason
docs(adr): remove ADR-NNNN — superseded by ADR-NNNN

These skills read from docs/adr/ by relative path — the wiki clone is transparent:

These skills may create ADRs in docs/adr/; the wiki push is handled at session end: