- Home
- /
- Categories
- /
- Git & VCS
Git & VCS
Git operations, commit helpers, branch management
code-story-teller
by tomwangowa
Analyze git history to tell the story of how code evolved. Use this Skill when the user asks to understand code history, explain evolution, show file timeline, or understand design decisions behind code.
Git Commit
by kadel
This skill should be used when the user asks to "commit changes", "create a commit", "commit my work", "stage and commit", "write commit message", "make a commit", or mentions committing code changes to a git repository.
rubait-relay
by ftpuser250
Git-based tool relay system for extending Claude's capabilities. Use this skill at the START of every conversation with Rubait to load system context, run cleanup, and enable tool calls via the GitHub relay repo (ftpuser250/claude). Trigger whenever Rubait says "continue where we left off", "use your tools", "check system status", or starts any technical session. Also trigger when creating new tools mid-conversation using tool_factory.
hotfix-workflow
by IHKREDDY
Rapid hotfix branch creation, fix application, and PR to main
home-assistant-apps
by Borales
Develop, configure, test, publish, and secure Home Assistant apps (formerly add-ons) — Docker-based extensions managed by the Supervisor. Use when creating new apps, writing Dockerfiles, configuring config.yaml, setting up Ingress, building repositories, implementing security best practices, or publishing to container registries.
sync-context
by xuesongjun
读档 - 快速恢复上次开发上下文
datum
by gitrdunhq
Automates the full software delivery cycle — brief to merged PR to closeout. Triggers: "datum go", "datum yolo", "datum <phase>", "datum resume", "datum status", "datum init", "run the epic", "start the development cycle", "let's implement this spec". Also activates when docs/epics//TICKET.md, docs/epics//SPEC.md, or TASKS.md is present.
git-convention
by yanix2445
Standard de référence pour la gestion de Git. Règles de sécurité, workflows atomiques, conventions de commit et bonnes pratiques de configuration.
simple-git-worktrees
by pproenca
This skill should be used when the user asks to "create worktree", "remove worktree", "work in worktree", "switch to worktree", "clean up worktree", mentions "repo--branch pattern", or during plan execution when worktree isolation is needed. Documents the sibling directory worktree pattern for simple, safe git worktree workflows.
pull-request
by junoh-moon
AUTOMATICALLY invoke this skill whenever PR creation is needed - no user request required. Direct gh pr create will FAIL validation. This skill contains required PR setup. Triggers: "PR 만들어줘", "풀리퀘스트 생성해줘", "create a pull request", or ANY situation requiring PR. For bucketplace organization repos, adds PR-by-AI label.
mantine
by ehyland
A fully featured React components library
code-review
by lct1407
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.
generate-pr-description
by Lichens-Innovation
Generate pull request descriptions by comparing current branch with parent branch. Creates semantic commit-style PR titles and fills PR templates. Use when the user asks to generate PR description, prepare pull request, or create merge request description.
git
by Alicoder001
Conventional Commits standard for consistent commit messages. Use when committing code, reviewing commit history, or setting up git workflows. Includes commit types, scopes, and breaking change format.
code-reviewer
by aleister1102
Use this skill to review code. It supports both local changes (staged or working tree)
github
by cuba6112
Automation of GitHub tasks using the gh CLI and REST API. Includes pagination strategies, payload construction, and rate limit management. Triggers: github, gh-cli, github-api, rate-limit, pagination, pull-request.
bug-issue
by Tmeister
Diagnose and fix a GitHub issue with a reproduction-first workflow.
ha-betriebshandbuch
by Patch76
HA-Betriebshandbuch für Claude-Instanzen — instanzunabhängiges Systemwissen für alle Home Assistant Installationen. Dieses Skill enthält das operative Wie und Was: API-Calls, Datei-Writes, Storage, Recorder, Diagnose. TRIGGER THIS SKILL WHEN: - Lesen, Schreiben oder Debuggen von HA REST API Calls - Anlegen oder Ändern von Automationen, Scripts, Szenen, Template-Sensoren - Storage-Dateien (.storage/) lesen oder schreiben - Helper (input_boolean, input_select, timer, etc.) anlegen oder löschen - Recorder-Konfiguration oder Datenbankzugriff - YAML-Dateien (automations.yaml, template.yaml, scripts.yaml) editieren - Zombie-Entities bereinigen - Backup vor destruktiven Aktionen - Zigbee-Bulbs steuern (Farbwechsel, Ein-/Ausschalten) - Android Companion App next_alarm Sensor nutzen - Statistiken reparieren (sum-Reset, Energy-Dashboard-Fehler, DB-Direktzugriff) NICHT TRIGGERN BEI: - Fragen nach Best Practices, Automations-Mustern oder Qualitätsregeln → dafür: home-assistant-best-practices - Auswahl zwischen Helfer-Typen oder Trigger-Arten (ob/warum, nicht wie) → dafür: home-assistant-best-practices - Dashboard-Layout, Card-Auswahl, Lovelace-Design → dafür: home-assistant-best-practices VORRANG: Betriebshandbuch = wie/was (Ausführung). Best-Practices = ob/warum (Design). Bei Überschneidung (z.B. Automation anlegen + Trigger-Muster-Frage): beide laden. NIEMALS RATEN — bei Unklarheit live testen oder API verifizieren.
property-test-generator
by nimiusrd
Design and generate property-based tests (PBT) for changed files in the current git branch. Extracts specifications, designs properties (invariants, round-trip, idempotence, metamorphic, monotonicity, reference model), builds generator strategies, implements tests, and self-scores against a rubric (24/30+ required). Supports fast-check (TS/JS), hypothesis (Python), and proptest (Rust). Use when: (1) "write property tests for my changes", (2) "add PBT", (3) "property-based test", (4) after implementing pure functions, validators, parsers, or formatters to verify invariants.
review
by ddaanet
Review in-progress changes for quality and correctness
gh-finish
by AutoFor
作業完了時に一気にマージまで実行する。ブランチ上なら PR 作成→マージ、main 上なら Issue・ブランチ作成から PR マージまで自動判定。
Code Review Skill
by pitzcarraldo
Question if the scope of changes is appropriate for the stated goal
scribe
by robdmc
Maintains a narrative log of exploratory work with file archives and git state tracking. Capabilities: (1) Log entries with propose-confirm flow, (2) Archive files linked to entries, (3) Capture git state (commit hash), (4) Create git commits with entry as message, (5) Restore archived files, (6) Query past work by time or topic, (7) Link related entries for thread tracking. Activates when user addresses "scribe" directly (e.g., "hey scribe, log this", "scribe, save this notebook", "scribe, what did we try yesterday?") or uses /scribe commands.
requesting-code-review
by Cygnusfear
Use when completing tasks, implementing major features, or before merging to verify work meets requirements