dotfiles

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Define, review, repair, or set up a repository's agent harness data flywheel: the learning loop that records agent sessions, learns from them by analysis or by replaying them on better models, applies the lessons to instructions, skills, hooks, and memory, prunes scaffolding newer models no longer need, and tunes the loop itself. Use when a repo documents a flywheel (docs/flywheel.md) that needs review or repair, when a repo has no learning loop and needs its first one, or when the user asks how agents should learn across sessions, keep memory, run retros or evals on recorded sessions, or remove harness scaffolding as models improve.

Define, review, repair, or set up a repository's agent harness data flywheel: the learning loop that records agent sessions, learns from them by analysis or by replaying them on better models, applies the lessons to instructions, skills, hooks, and memory, prunes scaffolding newer models no longer need, and tunes the loop itself. Use when a repo documents a flywheel (docs/flywheel.md) that needs review or repair, when a repo has no learning loop and needs its first one, or when the user asks how agents should learn across sessions, keep memory, run retros or evals on recorded sessions, or remove harness scaffolding as models improve.

Define, review, repair, or set up a repository's agent harness data flywheel: the learning loop that records agent sessions, learns from them by analysis or by replaying them on better models, applies the lessons to instructions, skills, hooks, and memory, prunes scaffolding newer models no longer need, and tunes the loop itself. Use when a repo documents a flywheel (docs/flywheel.md) that needs review or repair, when a repo has no learning loop and needs its first one, or when the user asks how agents should learn across sessions, keep memory, run retros or evals on recorded sessions, or remove harness scaffolding as models improve.

Check GitHub Actions CI status for PRs and branches. Use when the user asks "did CI pass", "check status", "what failed", "are checks green", "PR checks", "CI status", "workflow status", "re-run jobs", or wants a quick summary of GitHub Actions runs for a PR or the current branch.

Check GitHub Actions CI status for PRs and branches. Use when the user asks "did CI pass", "check status", "what failed", "are checks green", "PR checks", "CI status", "workflow status", "re-run jobs", or wants a quick summary of GitHub Actions runs for a PR or the current branch.

Diagnoses failing GitHub Actions runs by reading logs, identifying the root cause, and suggesting fixes. Use this skill whenever a user shares a GHA run URL, pastes runner log output, mentions a failing workflow, asks why a CI job is broken, or says anything like "my GHA is failing", "workflow failed", "can you check my run", or "CI is broken". Also trigger when raw log text is detected in the conversation that appears to come from a GitHub Actions runner. Do NOT use for general GHA workflow authoring questions, YAML formatting help, or passing runs with no failure context.

Diagnoses failing GitHub Actions runs by reading logs, identifying the root cause, and suggesting fixes. Use this skill whenever a user shares a GHA run URL, pastes runner log output, mentions a failing workflow, asks why a CI job is broken, or says anything like "my GHA is failing", "workflow failed", "can you check my run", or "CI is broken". Also trigger when raw log text is detected in the conversation that appears to come from a GitHub Actions runner. Do NOT use for general GHA workflow authoring questions, YAML formatting help, or passing runs with no failure context.

Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.

Delete local branches that have been merged or whose PRs are closed/stale

Create a git commit following the project's established style

Create a git commit following the project's established style

Intelligently push the current git branch to its remote with safety checks. Use when invoked as `$git-push` or when the user asks to push committed work.

Rebase the current branch onto a target branch using safety checks and an appropriate rebase strategy. Use when invoked as `$git-rebase` or when the user asks to update/rebase a branch.

Resolve unmerged paths from a pending merge, rebase, cherry-pick, or stash pop, then continue the operation and commit. Use when invoked as `$git-resolve-conflicts` or when the user asks to resolve conflicts and commit.

Split the most recent git commit into multiple logical commits without interactive rebase. Use when invoked as `$git-split` or when the user asks to split HEAD into smaller commits.

Stack an existing or new git branch on top of another branch, restacking it in a git worktree when needed, then align the GitHub PR bases and stack metadata with `gh stack`. Use when invoked as `$git-stack` or when the user asks to stack or restack a branch or PR onto another branch.

Intelligently analyze git status and provide insights about current project state

Intelligently analyze git status and provide insights about current project state

This skill should be used when the user asks to "scrub JSON values", "mask config fields", "add a Git clean filter", "remove volatile values from tracked config", or "stop config churn".