gh-attach: Skill for Claude Code

Probot Settings

Use this skill when a repository needs a new or updated .github/settings.yml managed by the Repository Settings GitHub App (repository-settings/app) or the older Probot Settings docs.

Step 0 — Determine Scope

Default to the current repository unless the user explicitly names another one.

gh repo view --json nameWithOwner -q .nameWithOwner
# Fallback:
git remote get-url origin

Step 1 — Gather the Current State

If .github/settings.yml already exists, read it first and update it surgically.

If the file does not exist yet, inspect the live repository and current labels:

REPO=<owner/repo>

gh repo view "$REPO" --json \
  name,nameWithOwner,description,homepageUrl,isPrivate,hasIssuesEnabled,hasWikiEnabled,defaultBranchRef,mergeCommitAllowed,rebaseMergeAllowed,squashMergeAllowed,deleteBranchOnMerge,repositoryTopics

gh label list --repo "$REPO" --json name,color,description --limit 200

Only inspect advanced sections when you actually plan to manage them:

• Branch protection: gh api repos/$REPO/branches/<branch>/protection
• Environments: gh api repos/$REPO/environments
• Teams / collaborators: inspect only for organisation-owned repositories

See references/sections-and-gotchas.md for section-level guidance.

Step 2 — Build the File from Minimal to Specific

Prefer a small, accurate file over a giant aspirational one.

1. Start with repository: and preserve the real repo name, description, homepage, visibility, default branch, and merge strategy.
2. Add labels: next; preserve existing labels unless the user wants a deliberate cleanup.
3. Add teams, collaborators, branches, environments, or milestones only when the repo already uses them or the user explicitly asks for them.
4. Keep comments short and useful; follow the existing file style if one already exists.

Use references/addono-examples.md for Addono-flavoured patterns and example repos.

Step 3 — Encode Important Upstream Rules