setup-matt-pocock-skills

Configure repository issue trackers, triage labels, and domain documentation layouts.

25|5|Updated Apr 22, 2017
One-click install
npx skills add https://github.com/assofohdz/subspace-infinity --skill setup-matt-pocock-skills-assofohdz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/assofohdz/subspace-infinity/tree/main/.agents/skills/setup-matt-pocock-skills
Command: npx skills add https://github.com/assofohdz/subspace-infinity --skill setup-matt-pocock-skills-assofohdz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the friction of engineering AI skills lacking critical context about a repository's issue tracking setup, triage label vocabulary, and domain documentation layout, which causes incorrect or failed outputs when performing repo-related tasks like issue creation, triage, and codebase diagnosis.

Core Features & Use Cases

  • Flexible Issue Tracker Configuration: Supports GitHub Issues, local markdown-based issue trackers, and custom third-party trackers like Jira or Linear.
  • Triage Label Mapping: Aligns the skill's canonical triage roles with the actual label vocabulary used in the repo's issue tracker to avoid duplicate or misapplied labels.
  • Domain Doc Layout Detection: Automatically detects single-context or multi-context repository structures to ensure skills like diagnose and improve-codebase-architecture read the correct domain and ADR files.
  • Use Case: For a Java game client repository like Subspace Infinity, run this skill first to configure GitHub as the issue tracker, use default triage labels, and set single-context domain doc rules so downstream engineering skills work correctly without manual context adjustment.

Quick Start

Use the setup-matt-pocock-skills skill to configure this repository's agent skill settings for issue tracking, triage labels, and domain documentation layout.

Frequently Asked Questions about setup-matt-pocock-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure AI agent skills for engineering workflows in a software repository?

Configuring AI agent skills for engineering workflows involves scaffolding per-repo configuration files that define issue tracker locations, triage label vocabulary, and domain documentation layout. This generates an Agent skills markdown block and supporting docs/agents/ documentation for consistent skill operation.

Why do engineering AI skills fail when performing issue triage and codebase diagnosis?

Engineering AI skills fail at issue triage and codebase diagnosis because they lack critical repository context including issue tracking setup, triage label vocabulary, and domain documentation layout. Configuring these per-repo settings ensures downstream skills read the correct domain and ADR files without manual adjustment.

Can I use local markdown issue trackers or custom third-party trackers with engineering AI skills?

Yes, engineering AI skills support flexible issue tracker configuration for GitHub Issues, local markdown-based issue trackers, and custom third-party trackers like Jira or Linear. The setup process maps canonical triage roles to your actual label vocabulary to avoid duplicate or misapplied labels.

How do I set up triage label mapping for a GitHub issue tracker in my repository?

Setting up triage label mapping for a GitHub issue tracker involves configuring per-repo agent skill settings that align the skill's canonical triage roles with the actual label vocabulary used in your repo's issue tracker. This prevents duplicate or misapplied labels during automated issue triage.

What's the best way to detect domain documentation layout for codebase architecture diagnosis?

The best way to detect domain documentation layout is using an agent skill setup tool that automatically identifies single-context or multi-context repository structures. This ensures engineering skills like diagnose and improve-codebase-architecture read the correct domain and ADR files.

Do I need to run setup skills before using engineering AI skills for issue creation and triage?

Yes, you need to run setup skills first to configure repository agent settings for issue tracking, triage labels, and domain documentation layout. Running this configuration first ensures downstream engineering skills work correctly without requiring manual context adjustment.