GitHubSkills

Fix failing GitHub Actions pipelines directly — detects broken workflows, reads run logs, diagnoses root causes, applies fixes in worktrees, and creates PRs. No prior repo scan or backlog required. Use this skill whenever the user wants to fix CI, repair a pipeline, debug Actions failures, or says things like "fix my pipeline", "fix CI", "my actions are failing", "fix my workflows", "repair my build", "CI is broken", "fix GitHub Actions", "debug my workflow", "why is my build failing", or "action fix". Do NOT use for scanning repos (use ghs-repo-scan), applying backlog items (use ghs-backlog-fix), or merging PRs (use ghs-merge-prs).

Applies backlog item fixes to a GitHub repository using parallel worktree-based agents — clones the repo once, creates git worktrees for each fix, launches agents simultaneously, verifies acceptance criteria, and creates PRs. Uses dependency-aware wave execution to prevent conflicts between related items and recalculates health scores after each wave for incremental progress. Persists session state for multi-session continuity. Use this skill whenever the user wants to apply, fix, or resolve a backlog item, references a project item, or says things like "apply this backlog item", "fix this issue", "resolve this finding", "work on this backlog item", "apply tier-1--license", or references an item in a GitHub Project. Also trigger when the user says "apply all backlog items", "fix all findings", "resolve all tier 1 items", or "apply all for {repo}". Do NOT use for scanning repos (use ghs-repo-scan), viewing backlog status (use ghs-backlog-board), or general code review.

Implement a GitHub issue using worktree-based agents, then create a PR. Clones the repo, creates a worktree, spawns an agent to implement the fix/feature, verifies the result, and opens a PR with auto-close references. For complex issues (High/Very High complexity from ghs-issue-analyze), automatically uses GSD framework for multi-phase planning and execution with wave-based parallelization, fresh context per task, and automated verification. Use this skill whenever the user wants to implement an issue, fix a bug from an issue, build a feature from an issue, or says things like "implement issue #42", "fix issue #42", "implement #42", "build feature from issue #15", "implement all triaged issues", "implement all bugs", "work on issue #42", "code issue #42", or describes work with no issue number like "owner/repo refresh readme" or "owner/repo fix the broken badge". Do NOT use for triaging/labeling issues (use ghs-issue-triage), analyzing issues (use ghs-issue-analyze), applying backlog health items (use ghs-ba

Shows a dashboard of all backlog items across all audited repositories — health scores, open issues, progress, and what to work on next. Use this skill whenever the user wants to see backlog status, check progress across repos, find the next item to fix, or asks things like "show backlog", "what's left to fix", "backlog status", "dashboard", "show all repos", "remaining items", "how are my repos doing", or "progress report". Also trigger when the user says "list backlog", "show findings", "show issues", or just "backlog". Do NOT use for scanning new repos (use ghs-repo-scan), applying fixes (use ghs-backlog-fix), or reviewing code. For quick "what should I work on next?" queries, prefer ghs-backlog-next instead.

Recommends the highest-impact next backlog item to fix across all audited repositories. Use this skill whenever the user wants a quick recommendation, asks "what should I work on next", "next item", "what's the most important fix", "highest impact item", "what to fix next", "priority item", "next action", or "recommend something to fix". Also trigger for "what's next" or just "next" in the context of backlog work. Do NOT use for full dashboards (use ghs-backlog-board), scanning repos (use ghs-repo-scan), or applying fixes directly (use ghs-backlog-fix).

Calculates and displays the health score for a repository from its backlog items. Use this skill whenever the user wants to see a repo's health score, check their score, recalculate after fixes, or says things like "what's my score", "show score for {repo}", "health score", "recalculate score", "how healthy is my repo", "score check", or "points breakdown". Do NOT use for full dashboards with issue lists (use ghs-backlog-board), scanning repos (use ghs-repo-scan), or applying fixes (use ghs-backlog-fix).

Promotes draft health items in a GitHub Project to real GitHub Issues for team visibility. Creates issues from draft items in the Todo column with Source = Health Check, replaces drafts with linked issues in the project, and copies custom field values. Use this skill whenever the user wants to sync health findings to GitHub Issues, promote draft project items to real issues, create issues from health checks, push findings to GitHub, publish health items for the team, or says things like "sync backlog", "create issues from health checks", "push findings to GitHub", "publish backlog", "sync health items", "sync findings to issues", "promote drafts", or "create GitHub issues from scan". Do NOT use for scanning repos (use ghs-repo-scan), applying fixes (use ghs-backlog-fix), or viewing backlog (use ghs-backlog-board).

Act as an autonomous developer for a repository — monitor for new/triaged issues, process them through the full development lifecycle (triage, analyze, implement, review, merge), handle health maintenance, dependency updates, and optional releases. Operates in cycles with human checkpoints for safety. Use this skill whenever the user wants a full developer loop, says things like "dev loop", "be my developer", "autonomous developer", "work on my repo", "process all issues", "developer mode", "full dev loop", "maintain this repo", "handle everything", "automate development", "dev cycle", "work through issues", "run a dev cycle", "be my dev", or "take over this repo". Do NOT use for single-skill operations — use the individual skill directly. Do NOT use for multi-repo pipelines — use ghs-orchestrate instead.

Deep-analyze a GitHub issue by inspecting the codebase and post a structured analysis comment with feasibility, complexity, affected files, suggested approach, and effort estimate. Use this skill whenever the user wants to analyze an issue, understand an issue before implementing it, get a complexity estimate, or says things like "analyze issue #42", "what would it take to fix #42", "assess this issue", "investigate issue #42", "how complex is issue #42", "issue analysis", "deep dive on issue #42", or "break down issue #42". Do NOT use for triaging/labeling issues (use ghs-issue-triage), implementing issues (use ghs-issue-implement), or scanning repo health (use ghs-repo-scan).

Verify and apply proper labels (type, priority, status) to GitHub issues — ensures a consistent label taxonomy exists on the repo, then classifies issues by type and priority. Use this skill whenever the user wants to label issues, triage issues, classify issues, organize issue labels, or says things like "triage my issues", "label all issues", "triage issue #42", "classify open issues", "add labels to issues", "auto-triage", "triage all --auto", or "set up issue labels". Do NOT use for analyzing issue implementation (use ghs-issue-analyze), implementing issues (use ghs-issue-implement), or scanning repo health (use ghs-repo-scan).

Merges pull requests on a GitHub repository — your own PRs, Renovate/bot PRs, or all eligible PRs at once. Use this skill whenever the user wants to merge PRs, asks to "merge my PRs", "merge renovate PRs", "merge all PRs", "merge PR #42", "clean up my pull requests", "merge and delete branches", "batch merge", "merge bot PRs", "merge dependency updates", or anything related to merging open pull requests. Also trigger for "merge all for {repo}", "squash merge renovate", "merge passing PRs", or just "merge" in the context of pull request work. Do NOT use for creating PRs (use ghs-backlog-fix), reviewing code, or scanning repos (use ghs-repo-scan).

Run a full maintenance pipeline across repositories — update, scan, fix, review, merge, sync, and optionally release. Chains existing ghs-skills in sequence with human checkpoints before destructive stages, state issue-based resume, and dry-run mode. Use this skill whenever the user wants to orchestrate a pipeline, maintain repos end-to-end, or says things like "orchestrate", "run pipeline", "maintain my repos", "full pipeline", "scan and fix all repos", "process all repos", "pipeline for {repo}", "run all skills", "maintenance run", "end-to-end maintenance", or "run the full workflow". Do NOT use for single skill invocations — use the individual skill directly.

Display a full 360-degree profile view of a GitHub user — profile info, repository portfolio, pinned repos, contribution stats, open work, organization memberships, and recent activity. Defaults to the authenticated user when no username is given. Use this skill whenever the user wants to see a GitHub profile, review their own activity, check someone's GitHub presence, or says things like "show my profile", "github profile", "who is {user}", "show @me", "my github stats", "what repos does {user} have", "contribution summary", "profile overview", "show github activity for {user}", "360 view", "user summary", or "profile report". Do NOT use for scanning repository health (use ghs-repo-scan), managing issues (use ghs-issue-triage), or fixing code (use ghs-backlog-fix).

Scaffold a new GitHub repository with all quality essentials to achieve a 100% health score from ghs-repo-scan. Creates the repo via `gh repo create`, generates all Tier 1/2/3 files tailored to the detected tech stack, configures repo settings via API, and verifies the result. For complex scaffolding (custom CI pipelines, monorepo setups), uses GSD framework for multi-phase execution. Use this skill whenever the user wants to create a new repo, scaffold a project, initialize a repository, bootstrap a project, or says things like "init project", "create repo", "scaffold repository", "new project", "project init", "initialize repo", "set up new repo", "bootstrap project", "create a 100% repo", "start a new project", or "create a perfect repo". Do NOT use for scanning existing repos (use ghs-repo-scan), fixing existing repos (use ghs-backlog-fix), or implementing issues (use ghs-issue-implement).

Create a GitHub Release with auto-generated changelog from merged PRs and conventional commits since the last release. Detects current version, determines the next semver bump, groups changes by type, and creates a tagged release with structured notes. Use this skill whenever the user wants to create a release, prepare a changelog, check what the next release would look like, or says things like "create release", "release v1.2.0", "patch release", "what would the next release look like", "changelog", "prepare release", "draft release", "pre-release", "cut a release", "tag a release", "ship it", or "what changed since last release". Do NOT use for merging PRs (use ghs-merge-prs), fixing backlog items (use ghs-backlog-fix), scanning repo health (use ghs-repo-scan), or managing GitHub Actions (use ghs-action-fix).

Scans a GitHub repository for quality essentials and open issues, produces a scored report, and saves all findings as items in a GitHub Project. Use this skill whenever the user wants to check repository quality, audit a repo's setup, see open issues organized as backlog, verify best practices are followed, or asks about missing files like README, LICENSE, CODEOWNERS, CI/CD, branch protection, templates, security policies, .editorconfig, or failing CI workflows. Also trigger when users say things like "scan my repo", "is my repo set up properly", "what's missing from my project", "repo audit", "repo scan", "repository checklist", "health check", "what issues are open", "organize my issues", "save health report", "export audit results", or "create backlog from audit". Do NOT use for managing GitHub Actions workflows, reviewing pull requests, creating repositories, or modifying code.

Pull (update) all locally cloned repositories in the repos/ directory. Trigger: "pull all repos", "update all repos", "git pull repos", "refresh repos", "sync repos"

Review a GitHub pull request by fetching the diff, analyzing code changes against the codebase, and posting a structured review comment with findings by severity. Use this skill whenever the user wants to review a PR, check code quality, or says things like "review PR #42", "review my PRs", "code review", "check PR #42", "review all open PRs", "review PRs by renovate", "what does PR #42 change", "is PR #42 safe to merge", "review draft PRs", or "review ready PRs". Do NOT use for merging PRs (use ghs-merge-prs), implementing issues (use ghs-issue-implement), or scanning repo health (use ghs-repo-scan).