Loading...
Loading...
Found 278 Skills
Read this skill before creating any git commit to ensure the commit message matches the project's established patterns. Triggers on: git commit, /commit, creating commits, or any task that results in a git commit.
Split changes into a Graphite stack with PR titles and descriptions. Use when asked to create or propose a stacked PR series.
Execution-type Core-Lite Git worktree skill (only supports help/init/do/check/merge). Default execution without parameters is init --new + do exec; high-risk commands are only permitted via the CLI latch --yes --i-am-maintainer; lock conflicts default to SAFE_NEXT=init --new. Execution commands only read route-bash/route-powershell.
Use when asked to fix, resolve, or address a GitHub PR — including review comments, Copilot suggestions, and CI test failures. Triggers on phrases like "fix PR", "fix PR comments", "resolve review", "address Copilot feedback", "fix review comments", "fix CI", "fix failing tests on PR", or when given a PR number to fix.
Structured TODO commit workflow using JJ (Jujutsu). Use to plan tasks as empty commits with [task:*] flags, track progress through status transitions, manage parallel task DAGs with dependency checking. Enforces completion discipline. Enables to divide work between Planners and Workers. **Requires the working-with-jj skill**
Git commit message best practices. Use when writing commit messages, reviewing commits, or setting up commit conventions for a project. Ensures clear, consistent, and useful commit history.
Commit standards for Engram contributors. Trigger: Any commit creation, review, or branch cleanup.
Summarize code changes by author type and scope. Inputs are author and scope with product plus PR as defaults.
Compare files and directories between git worktrees or worktree and current branch
Generate Git branch names from staged or branch changes
Maintains CHANGELOG.md following Keep a Changelog format and Semantic Versioning. Use when the user mentions preparing or publishing a new release, or asks to review or refactor CHANGELOG.md.
Clean up local branches after PR merges. Syncs main with origin, identifies branches with merged PRs, and proposes safe deletion. Use when the user asks to 'clean up branches', 'delete merged branches', 'sync branches', or mentions branch cleanup.