setup-matt-pocock-skills

Configure repositories with issue tracker settings, triage labels, and documentation structure.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Lev-it/lev-skills --skill setup-matt-pocock-skills-lev-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-matt-pocock-skills
Source: https://github.com/Lev-it/lev-skills/tree/main/.claude/skills/setup-matt-pocock-skills
Command: npx skills add https://github.com/Lev-it/lev-skills --skill setup-matt-pocock-skills-lev-it

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Streamlines the initial configuration of engineering skill sets by automating setup for issue trackers, triage labels, and domain documentation layout, enhancing the efficiency of skill integration into a repository.

Core Features & Use Cases

  • Automated Issue Tracker Configuration: Automatically identifies and configures issue tracking systems like GitHub, GitLab, or local markdown, saving time on manual setup.
  • Triage Label Vocabulary Setup: Facilitates the creation of a consistent and usable label vocabulary for effective issue management.
  • Domain Documentation Layout Confirmation: Helps ensure proper placement of documentation such as CONTEXT.md and architectural decision records (docs/adr/), for optimal skill performance.

Quick Start

Initialize the setup for Matt Pocock's engineering skills in your repository using the command: 'npx setup-matt-pocock-skills'.

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 set up issue tracking and triage labels in a new repository?

To set up issue tracking and triage labels, you can automate the initial repository configuration to establish a consistent label vocabulary and issue tracker settings, saving time on manual setup for Git-based platforms like GitHub or GitLab.

What is the best way to structure domain documentation and ADRs for engineering skills?

Structuring domain documentation for engineering skills involves placing a `CONTEXT.md` file at the root and architectural decision records inside a `docs/adr/` directory, ensuring proper documentation layout for optimal skill performance.

Does this automated repository setup work with local markdown issue trackers?

Yes, the automated repository setup works with local markdown issue trackers, alongside GitHub and GitLab, by identifying the Git-based environment and configuring the necessary issue tracking system settings accordingly.

How do I initialize triage label configurations and domain docs together?

You can initialize triage label configurations and domain docs together by running an automated setup command, which configures the issue tracker settings, establishes the label vocabulary, and confirms the documentation layout in one pass.

Why do I need a CONTEXT.md file and ADRs for my engineering skills setup?

A `CONTEXT.md` file and ADRs are needed because they provide the necessary domain documentation structure and architectural context, ensuring that engineering skills function correctly within the repository environment.

Can I use this setup tool to configure issue trackers for existing GitLab projects?

Yes, you can use this setup tool to configure issue trackers for existing GitLab projects, as it identifies the active Git-based issue tracking system and applies the required triage labels and domain documentation layout.