Configure the repository
SkillDocs & knowledgeConfigure repository-local tracker, triage, and domain-document conventions needed by the Matt Pocock engineering skills.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Configure the repository skill
What this skill tells your AI
The instructions your AI receives, as published by stevesolun/ctx in .agents/skills/setup-matt-pocock-skills/SKILL.md and read by ahel’s review.
- Inspect existing tracker conventions, remotes, domain documents, ADRs, and skill configuration. Reuse established structure.
- Determine which configuration the installed workflows actually need: issue-tracker guidance, triage labels, domain-document guidance, or a subset.
- Infer unambiguous choices from the repository. Ask only about choices that materially change behavior, and present a recommendation with the tradeoff.
- Show the proposed repository-local files before writing when the choice is material or the files already contain user decisions.
- Write the smallest idempotent configuration that satisfies the selected
workflows. Do not add skill inventories or workflow prose to
AGENTS.mdorCLAUDE.md; keep those files lightweight and point workflows at dedicated configuration instead. - Report what was configured and what remains intentionally unconfigured.
Use the existing seed files only for the selected branch:
- GitHub: issue-tracker-github.md
- GitLab: issue-tracker-gitlab.md
- Local Markdown: issue-tracker-local.md
- Triage labels: triage-labels.md
- Domain documents: domain.md
Adapt templates to the repository; they are references, not required output shapes.
Signals
- GitHub stars
- 585
- Forks
- 71
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
setup-matt-pocock-skills-stevesolun- Source
- github.com/stevesolun/ctx