skills.rest
ajrmooreuk
ajrmooreukCOMMUNITY
Explore all skills by this author →
GitHub

setup-repo

Provision GitHub repositories with Azlan workflow labels and branch protection.

Updated Feb 17, 2026
Search Tags:#workflow#github#setup#labels#project-board#branch-protection#azlan
One-click install
npx skills add https://github.com/ajrmooreuk/pfi-w4m-dev --skill setup-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-repo
Source: https://github.com/ajrmooreuk/pfi-w4m-dev/tree/main/azlan-github-workflow/skills/setup-repo
Command: npx skills add https://github.com/ajrmooreuk/pfi-w4m-dev --skill setup-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provisions a GitHub repository with the full Azlan workflow conventions to standardize labels, branch protection, and project board setup when creating or updating repos.

Core Features & Use Cases

  • Create and apply standard labels (e.g., type:epic, type:feature, type:story) to ensure consistency across repositories.
  • Configure main-branch protection and workflow settings in solo or team mode.
  • Generate a setup report summarizing labels, protection status, and recommended next steps.

Quick Start

Run the setup-repo skill with your owner/repo and optional mode to initialize labels, protections, and a project board for the repository.

Frequently Asked Questions about setup-repo

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

FAQPage Schema
How do I set up standard labels and branch protection on a new GitHub repository?▼

You can provision a GitHub repository with standardized workflow conventions by applying consistent labels such as type:epic and type:feature, and configuring main-branch protection rules automatically.

What is the best way to configure a GitHub project board for solo versus team development?▼

Configuring a GitHub project board for solo or team development requires applying specific workflow modes. You can provision repositories with either solo or team mode to standardize project board setup and branch protection settings accordingly.

Can I apply standardized GitHub labels to an existing repository?▼

Yes, you can apply standardized GitHub labels to an existing repository. The setup workflow supports both new and existing repositories, creating missing labels and enforcing branch protection configurations.

How do I enforce main-branch protection rules across multiple GitHub repositories?▼

Enforcing main-branch protection rules across repositories involves applying a standardized workflow convention. You can provision each repository with argument parsing for owner and repo names, configuring branch protection automatically based on solo or team mode.

What standard GitHub labels should I use for feature tracking and issue management?▼

Standard GitHub labels for feature tracking include type:epic, type:feature, and type:story. Applying these standardized labels ensures consistency across repositories for issue management and project board organization.

Related Skills

Explore More Software Engineering Skills→
CyapstayeCyapstaye
9

github-repo-management

Manage GitHub repository lifecycles, releases, and workflows via CLI or REST API.

Community
Intermediate
rodacatorodacato

github

Configure GitHub repositories with standard labels, templates, workflows, and branch protections.

Community
Advanced
yasuwrldhyperyasuwrldhyper

gh-cli

Manage GitHub repositories, issues, pull requests, and Actions via CLI.

Community
Advanced
shellicarshellicar

github-repos

Configure GitHub repository settings and enforce branch protection rules via the gh CLI.

Community
Intermediate