Loading...
Loading...
Found 33 Skills
Test-Driven Development enforces the RED-GREEN-REFACTOR discipline on every code change an agent produces.
Turn the working tree into logical, atomic Conventional Commits — classify uncommitted files as in-scope vs out-of-scope against the branch's merge base, show a staging plan, and create one commit per coherent unit (type + optional scope + British-English body; `!` / `BREAKING CHANGE:` for breaking changes). Never `git add -A`; files that look like they belong to another branch/worktree are never staged silently. Use when asked to commit uncommitted work, tidy WIP into atomic commits, or as the commit step inside a ship flow (e.g. `/send-it`). It commits only — no push, PR, changelog, or Linear writeback.
Create atomic user-approved commits with `feat`/`fix`/`chore` titles and finalise branch merge/cleanup with tracking sync. Triggers: commit changes, split commits, finalise branch, commit message.
Git workflow management with atomic commit principles. Capabilities: commit organization, branching strategies, merge/rebase workflows, PR management, history cleanup, staged change analysis, single-responsibility commits. Actions: commit, push, pull, merge, rebase, branch, stage, stash git operations. Keywords: git commit, git push, git pull, git merge, git rebase, git branch, git stash, atomic commit, commit message, conventional commits, branching strategy, GitFlow, trunk-based, PR, pull request, code review, git history, cherry-pick, squash, amend, interactive rebase, staged changes. Use when: organizing commits, creating branches, merging code, rebasing, writing commit messages, managing PRs, cleaning git history, analyzing staged changes.
Create atomic conventional git commit and push to remote repository. Use when committing staged changes with conventional commit format and immediately pushing to the remote branch.
Monorepo migration orchestrator for scripted import path changes, package renames, and module moves with verification gates. Use when user mentions: - "migrate import paths" - "rename this workspace package" - "bulk module reorganization"
Creates git commits. Use this skill whenever the user asks to commit, or whenever you need to commit changes as part of a task.
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
Structured git commit messages following Conventional Commits format for Go projects. Generates well-scoped, atomic commits with clear descriptions. Use when committing changes, writing commit messages, preparing PRs, or reviewing commit history quality. Trigger examples: "commit these changes", "create commit", "commit message", "prepare PR", "squash commits". Do NOT use for changelog generation (use changelog-generator) or code review (use go-code-review).
Encodes the user's git commit conventions (Conventional Commits with a short title and a concise pointwise body, and atomic commits made only when a logical change is complete). Use when writing commit messages, staging or committing changes, squashing, or when asked to "commit this", "write a commit message", or "make a commit".
Create high-quality Pull Requests with conventional commits and proper descriptions. Trigger: When creating PRs, writing PR descriptions, or using gh CLI for pull requests.
Create git commits with user approval and no Claude attribution