Loading...
Loading...
Found 20 Skills
Git Commit Rules
Commit message format, logical grouping, and branch naming rules. Follow when creating git commits, branches, or PRs.
Create semantic git commits following best practices and Conventional Commits specification.
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
List recent git commits that are linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", or wants a list of commits with their session context.
Help create git commits and PRs with properly formatted messages and release notes following CockroachDB conventions. Use when committing changes or creating pull requests.
Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work
Help create git commits and PRs with properly formatted messages and release notes following CockroachDB conventions. Use when committing changes or creating pull requests.
Review, organize, and commit pending changes. Split into logical commits, stage carefully, and write clear Conventional Commit messages. Use when the user asks to commit, stage changes, or organize work into commits.
Review code changes against a plan using the plan location and implementing git commit(s).
Creates git commits. Use this skill whenever the user asks to commit, or whenever you need to commit changes as part of a task.
Create and execute Git commits in Conventional Commits format with a required body. Use when the user asks to commit changes, write commit messages, or prepare a clean commit. Always run a pre-commit safety guard first, abort on log files or untracked high-risk binary extensions, then stage with `git add . -A`.