---

name: repo-config description: Use when needing to get the default branch, detect repository settings, fetch available labels, get repo info for API calls, or when any gh-workflow command needs dynamic repository configuration instead of hardcoded values. version: 1.0.0

Repository Configuration

This skill provides dynamic repository configuration for all gh-workflow commands, auto-detecting settings so commands work in any repository without hardcoding.

Use TodoWrite to track these mandatory steps:

Quick Reference

Get Repository Info

Copy# Full repository details
gh repo view --json name,owner,defaultBranchRef,url,description

# Just the default branch
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'

# Repository owner/name
gh repo view --json nameWithOwner --jq '.nameWithOwner'

Get Labels

Copy# List all labels (always fetch dynamically, never hardcode)
gh label list

# Check if specific label exists
gh label list --search "bug"

Detect Branch Naming Convention

Copy# Analyze existing branches for patterns
git branch -r --list 'origin/feature/*' | head -5
git branch -r --list 'origin/fix/*' | head -5

# Check recent branch names
git for-each-ref --sort=-committerdate --format='%(refname:short)' refs/remotes/origin/ | head -10

Detect Commit Convention

Copy# Analyze recent commits for patterns
git log --oneline -20 | head -20

Configuration Detection

Default Branch

Always detect dynamically:

CopyDEFAULT_BRANCH=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')

Common values: main, master, develop

Repository Identification

Copy# Get owner/repo for API calls
REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')

# Use in gh api calls
gh api repos/$REPO/pulls/123/comments

Label Strategy

Never hardcode labels. Always fetch dynamically:

Copy# Get available labels
gh label list

# Present to user with AskUserQuestion tool
# Let user select from actual available labels

Branch Naming Patterns

Detect from existing branches or use defaults:

Commit Conventions

Detect or default to conventional commits:

Usage in Commands

Before Any Repository Operation

Copy# Step 1: Get repo info
REPO_INFO=$(gh repo view --json nameWithOwner,defaultBranchRef)
REPO=$(echo $REPO_INFO | jq -r '.nameWithOwner')
DEFAULT_BRANCH=$(echo $REPO_INFO | jq -r '.defaultBranchRef.name')

# Step 2: Use detected values
gh pr create --base $DEFAULT_BRANCH ...
gh api repos/$REPO/pulls/123/comments

For Label Operations

Copy# Step 1: Fetch available labels
gh label list

# Step 2: Use AskUserQuestion tool to let user select
# Step 3: Apply selected labels
gh issue create --label "selected-label"

Best Practices

Integration Points

All gh-workflow commands should:

1. Reference this skill for configuration patterns
2. Use dynamic detection instead of hardcoded values
3. Fall back to sensible defaults if detection fails
4. Use the AskUserQuestion tool when user input is needed

Grep Patterns

To find configuration usage in the codebase:

Copy# Find hardcoded branch references
grep -r "main\|master" --include="*.md" plugins/

# Find label references
grep -r "label" --include="*.md" plugins/

# Find gh repo commands
grep -r "gh repo\|gh issue\|gh pr" --include="*.md" plugins/

Error Handling

If gh commands fail, check:

• Is the user authenticated? gh auth status
• Is this a git repository? git rev-parse --git-dir
• Does the repository have a GitHub remote? git remote -v

Report clear, actionable error messages.