Git & VCS
Git operations, commit helpers, branch management
commit
by tkersey
Create micro-commits (minimal incision) with at least one validation signal per commit. Use when requests say "split this into micro commits," "stage only the minimal change and commit," "keep commits tiny while checks pass," or when parallel workers/slices need isolated, reviewable commits.
patch
by tkersey
Create micro-patches from staged git changes (minimal incision) with at least one validation signal per patch. Use when asked to split work into small .patch files, export/share diffs, or produce patches instead of commits.
burette-pr-body
by SergeiNikolenko
Prepare or revise a Burette GitHub pull request title and body from the actual net change.
fin
by tkersey
"Finalize GitHub PRs end-to-end: update branch/PR, monitor CI until green, squash-merge, and clean up local/remote state. Use when asked to $fin or to finish/land/merge/close a PR, watch checks or runs, squash-merge, delete the branch, and sync local state."
burette-code-review
by SergeiNikolenko
Run a final multi-angle code review on a Burette branch or pull request.
learnings
by tkersey
"Capture and persist evidence-backed execution learnings into .learnings.jsonl. Trigger cues/keywords: $learnings, lessons learned, takeaways, wrap up, handoff, before commit/PR, after tests pass, fail-to-pass, strategy pivot, footgun, retry loop."
mesh
by tkersey
Swarm coordinator activated only by explicit $mesh invocation. Trigger cues/keywords: orchestrate subagents/workers, execute ready $st slices/tasks, run propose/critique/synthesize/vote cycles, coordinate concurrent workers, require consensus + validation before completion, and persist learnings via $learnings.
study-notes-creator
by szeyu
Create organized, visual study notes with folder structures, diagrams, and example-based learning from source materials (PDFs, lecture notes, documentation). Use when creating structured learning materials, exam preparation notes, or educational documentation. Triggers - organize study notes, create visual learning materials, generate notes with diagrams, exam prep notes, example-based learning.
xit
by tkersey
"Use when a repo has .xit/ or the user asks for xit: translate git-like intents to non-interactive xit CLI commands (status/diff/log --cli, add/commit/branch/merge/cherry-pick), avoid the TUI, and do not use git unless explicitly requested."
join
by tkersey
"PR autopilot via gh only: create/manage PRs, keep branches current, enforce required CI gates, apply surgical code patches, and publish merge-ready handoff without merging. Use when asked to run or monitor PR automation, fix failing required checks, keep local/remote branch state clean, or prepare branch/PR cleanup for human merge."
burette-release-readiness
by SergeiNikolenko
Review Burette release readiness for versioning, packaging, signing, updates, installers, and package managers.
build-a-skill
by avibe-bot
"Use when creating or modifying a skill: follow SKILL.md rules, define commands and dependencies, validate locally, version correctly, and publish"
discover-a-skill
by avibe-bot
"Use when you need new capabilities: discover skills, inspect details, install to agents, run commands, and manage updates with askill"
draft-pr
by benmatselby
Create a draft pull request for the current branch. Summarises the diff, fills in any PR templates, and opens the PR via the gh CLI.
git-log-summary
by benmatselby
Provides a summary of the git log for the past period of time. Use when asked to provide a git log summary.
github-issue-analyzer
by benmatselby
Analyzes a GitHub issue by fetching its details and exploring the relevant codebase to identify the root cause and suggest solutions. Use when given a GitHub issue URL to investigate.
python-clean-code
by ertugrul-dmr
Use when writing, fixing, editing, reviewing, or refactoring any Python code. Enforces Robert Martin's complete Clean Code catalog—naming, functions, comments, DRY, and boundary conditions.
commit-messages
by TheDecipherist
Generate clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or preparing releases.
HumpDay code-review skill
by microprediction
Repository: <https://github.com/microprediction/humpday>
daily-releases
by Jamie-BitFlight
'Create GitHub Releases with AI-analyzed changelogs for every calendar day with commits on origin/main. Use when creating daily release notes, backfilling releases, or generating AI-categorized changelogs per day. Uses collect → bucket → analyze → synthesize → publish pipeline via Haiku subagents. Idempotent — skips up-to-date days, updates releases where new commits were added. Accepts optional --start-date, --end-date, --branch, and --dry-run arguments.'
start-milestone
by Jamie-BitFlight
"Transitions a GitHub milestone from planning to active execution. Use when the team is ready to begin a sprint or release cycle — bulk-transitions open issue labels from status:needs-grooming to status:in-progress, updates GitHub Projects V2 Status to In Progress, and confirms before applying changes. Requires milestone number as argument. Use after /group-items-to-milestone."
git-history-recon
by Jamie-BitFlight
Analyze git repository history to produce a codebase risk profile before code review. Probes repo size, runs 7 parallel git analysis pipelines (hotspots, bug magnets, bus factor, contributor momentum, firefighting frequency, newly added files), cross-references hotspots with bug magnets to identify high-risk files with primary owner annotation, and writes walkthrough/recon-report.md. Use before code review to prioritize reviewer attention, at the start of linear-walkthrough Phase 1 Discovery to weight file coverage, or when onboarding to an unfamiliar codebase.
dev-self-merge
by loopdive
Merge self-check for a green PR. Reads the PR's required-check status from the checks API (the committed ci-status feed is RETIRED), outputs MERGE (mark task completed, stand down — server-side auto-enqueue enqueues, #2786) or ESCALATE. Devs do NOT enqueue.
claim-issue
by loopdive
Atomically claim an issue for a developer (human or agent) via the cross-developer lock ref, so two devs never pick up the same task. Syncs with origin first, refuses if already claimed or already done on main, and pushes the claim immediately without touching main or triggering CI.