Configure the Engineering Skills for Your Repository

What it does

This is a configuration interview rather than a generic installer. It first inspects existing steering files, Git remotes, glossary documents, architecture records and monorepo signals. The source prefers an existing CLAUDE.md or AGENTS.md over creating a competing entry point. Tracker behavior lives in pointed-to documents, while the steering file carries short summaries. Triage labels are configured only when triage is present. A single glossary context is the default unless the repository actually needs multiple contexts.

When to use it

• Connect an existing GitHub project to the collection’s issue workflows.
• Use local Markdown tickets for a solo repository without a remote tracker.
• Preserve custom triage labels while making their roles explicit.

Step-by-step workflow

1. Inspect existing instructions, remote configuration and domain documentation.
2. Confirm the actual tracker and verify repository access where applicable.
3. Choose triage-role mappings only if the triage workflow is available.
4. Present the proposed steering block and referenced documents for review.
5. Merge approved configuration into existing files and verify the pointers.

Example request

Use setup-matt-pocock-skills to prepare this repository for local Markdown issues. Inspect existing AGENTS.md and glossary files first. Preserve our existing instructions and do not add a second steering file. Triage is not installed, so omit its labels. Show the proposed tracker and domain-document configuration before editing. Do not create remotes, publish issues or change external labels.

Worked example

A solo project may already keep feature notes under .scratch. The setup can capture that convention instead of assuming GitHub Issues. If a root glossary exists, pointing to it is more useful than inventing a monorepo map. A second run should update the existing Agent skills block, not append another copy. For a remote tracker, success means the configured CLI can identify the correct project; writing its URL into a document alone is insufficient.

What you get

A reviewed steering-file section and project-specific tracker, domain and optional triage documents.

How to evaluate the result

• Verify every context pointer resolves to a real document.
• Confirm rerunning updates the existing block without duplication.
• Check label setup is omitted when triage is absent.

What you need

Repository access, existing conventions, the source’s seed templates and an owner who can decide tracker behavior. GitHub or GitLab use needs its corresponding authenticated CLI.

Setup and activation

The publisher documents plugin setup for Claude Code, Codex and Copilot, and manual Agent Skills setup for Gemini CLI and other clients. Choose one distribution method per client to avoid duplicate skills. The engineering collection expects project-specific tracker, triage-label and document-location settings from setup-matt-pocock-skills. Keep referenced companion skills and files available. This catalogue review does not install or run them; scan the exact source before any later installation. Client tools, permissions and subagent support still need separate validation.

Limits and considerations

The upstream flow can initialize Git, add a remote and create labels. Those actions must fit actual user authorization. This review neither installs the collection nor tests client compatibility. Preserve surrounding instruction-file edits.

Related workflows

• Use to-tickets after tracker configuration is settled.
• Use domain-modeling to maintain the agreed vocabulary.

License and reuse

MIT at repository level (Copyright 2026 Matt Pocock). Preserve the copyright and permission notice when redistributing substantial source material; inspect any separately licensed dependencies or assets.

Further reading

• Reviewed SKILL.md (immutable commit)
• Publisher README: distributions and compatibility
• Reviewed MIT license