No Rust code, migrations, or runtime behavior changes — tooling + docs only.
Evidence
tea issues list succeeds against git.crkc.xyz (Gitea 1.27.3, issues
enabled, deps enabled) — the tracker surface documented in docs/agents/issue-tracker.md is live.
git check-ignore: docs/agents/domain.md now tracked (exit 1), docs/adr still ignored (exit 0) — the ignore rule change behaves as intended.
Symlinks are relative (../../.agents/skills/<name>), verified with readlink; they resolve correctly in the working tree and survive clone.
Merge Danger
Door: two-way — git revert of this commit removes everything cleanly;
no migrations, no schema, no API surface touched.
Blast Radius: agent tooling only. Worst case an agent reads a wrong docs/agents/*.md convention; no effect on server behavior, CI, or the
Rust codebase. The .gitignore change is scoped: only docs/agents/
gains tracking; the local /docs/* tree remains ignored.
One thing to sanity-check on first real use: the /wayfinder blocking
edge command (tea api .../dependencies/blocked_by) is documented but not
exercised live yet.
## Summary
Installs the 38 mattpocock/skills into this repo and scaffolds the per-repo
agent config the engineering skills assume:
```text
.agents/skills/ # 38 skills (single source of truth)
├── triage/ # reads docs/agents/*.md
├── to-tickets/ to-spec/ # read + write the issue tracker
├── wayfinder/ # wayfinding ops on Gitea issues
└── ...
.claude/skills/ # 38 relative symlinks → ../../.agents/skills/*
skills-lock.json # pins the install for reproducible re-runs
docs/agents/ # NEW: per-repo agent config
├── issue-tracker.md # Gitea (git.crkc.xyz) via `tea` CLI
├── triage-labels.md # default 5-role label vocabulary
└── domain.md # single-context: CONTEXT.md + docs/adr/
CLAUDE.md # + "## Agent skills" section pointing at docs/agents/
.gitignore # /docs → /docs/* (un-ignore docs/agents/; local /docs stays out)
```
No Rust code, migrations, or runtime behavior changes — tooling + docs only.
## Evidence
- `tea issues list` succeeds against git.crkc.xyz (Gitea 1.27.3, issues
enabled, deps enabled) — the tracker surface documented in
`docs/agents/issue-tracker.md` is live.
- `git check-ignore`: `docs/agents/domain.md` now tracked (exit 1),
`docs/adr` still ignored (exit 0) — the ignore rule change behaves as intended.
- Symlinks are relative (`../../.agents/skills/<name>`), verified with
`readlink`; they resolve correctly in the working tree and survive clone.
## Merge Danger
**Door:** two-way — `git revert` of this commit removes everything cleanly;
no migrations, no schema, no API surface touched.
**Blast Radius:** agent tooling only. Worst case an agent reads a wrong
`docs/agents/*.md` convention; no effect on server behavior, CI, or the
Rust codebase. The `.gitignore` change is scoped: only `docs/agents/`
gains tracking; the local `/docs/*` tree remains ignored.
One thing to sanity-check on first real use: the `/wayfinder` blocking
edge command (`tea api .../dependencies/blocked_by`) is documented but not
exercised live yet.
- 38 skills from mattpocock/skills into .agents/skills/ (symlinked into
.claude/skills/ for Claude Code)
- skills-lock.json for reproducible installs
- docs/agents/: issue-tracker (Gitea via tea CLI), triage-labels
(default five-role vocabulary), domain docs (single-context)
- CLAUDE.md: add '## Agent skills' section pointing at docs/agents/
- .gitignore: un-ignore docs/agents/ under the local /docs/* rule
cameron
merged commit bf64d046d8 into master2026-09-24 17:31:51 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Installs the 38 mattpocock/skills into this repo and scaffolds the per-repo
agent config the engineering skills assume:
No Rust code, migrations, or runtime behavior changes — tooling + docs only.
Evidence
tea issues listsucceeds against git.crkc.xyz (Gitea 1.27.3, issuesenabled, deps enabled) — the tracker surface documented in
docs/agents/issue-tracker.mdis live.git check-ignore:docs/agents/domain.mdnow tracked (exit 1),docs/adrstill ignored (exit 0) — the ignore rule change behaves as intended.../../.agents/skills/<name>), verified withreadlink; they resolve correctly in the working tree and survive clone.Merge Danger
Door: two-way —
git revertof this commit removes everything cleanly;no migrations, no schema, no API surface touched.
Blast Radius: agent tooling only. Worst case an agent reads a wrong
docs/agents/*.mdconvention; no effect on server behavior, CI, or theRust codebase. The
.gitignorechange is scoped: onlydocs/agents/gains tracking; the local
/docs/*tree remains ignored.One thing to sanity-check on first real use: the
/wayfinderblockingedge command (
tea api .../dependencies/blocked_by) is documented but notexercised live yet.