- Home
- /
- Categories
- /
- Git & VCS
Git & VCS
Git operations, commit helpers, branch management
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.
Rafter -- Security Toolkit for AI Coding Agents
by Raftersecurity
```
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
using-commit
by jrodrigopuca
Guía para escribir mensajes de commit siguiendo Conventional Commits. Usar cuando se vaya a realizar un commit, crear mensajes descriptivos, estandarizar el historial del proyecto, o automatizar versionado y changelogs. Incluye tipos de commit, scopes, breaking changes, formato y mejores prácticas. Activar con frases como "hacer commit", "mensaje de commit", "conventional commits", o "escribir commit semántico".
resolve-pr-feedback
by jkappers
Resolve open PR review discussions by evaluating applicability and value, then fixing valid feedback with conventional commits. Use when (1) addressing reviewer feedback on a pull request, (2) resolving open PR discussions systematically, (3) triaging PR review comments for actionability, (4) batch-fixing code review feedback, or (5) cleaning up unresolved PR conversations.
git-worktree-feature-flow
by alessandrobologna
Create a feature branch in a Git worktree, work independently, then merge back and clean up safely.
dev-tools
by Olino3
Essential development workflow agents for code review, debugging, testing, documentation, and git operations. Orchestrates multi-step developer workflows by composing existing skills into streamlined pipelines. Triggers: step
backend-reviewer
by shaul1991
Backend Reviewer Agent. 코드 리뷰, PR 검토, 코드 품질 평가를 담당합니다. 리뷰, 검토, PR, 코드 품질 관련 요청 시 사용됩니다.
momenta-ppt
by yutingzhou0202
生成或润色 Momenta 风格 PPT。当用户要求制作新 PPT、对已有 PPT 进行格式修改/润色,或提供飞书文档链接要求转化为 PPT 时触发。
start-new-app
by queso
Scaffolds a new app from the context-kit template. Clones the repo, renames the project, initializes git, creates a PRD directory, and asks the user to provide a PRD.
deslop-code
by heykvnzhao
Clean up AI-generated code changes by reviewing diffs against main and removing stylistic or structural artifacts (over-commenting, unnecessary defensive checks, try/catch noise, any-casts, inconsistent style). Use when asked to “remove AI code slop,” “humanize” changes, or align a branch’s edits with existing codebase conventions.
task-management
by xfwgithub
零依赖、高性能的任务管理技能。当用户需要创建、查询、更新、删除任务或获取任务统计时使用此技能。
veil
by ushiradineth
Route agent tasks to Veil CLI commands with a practical local-first then web workflow.
ghwf3-plan
by ShotaIuchi
実装計画ドキュメントを作成
git-pushing
by pm-minji
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
repo-issue-triage
by spboyer
Automate GitHub issue and PR triage by cross-referencing open issues against pending PRs, merged PRs, and the current main branch to produce an actionable report with close/keep recommendations. Includes PR health monitoring. USE FOR: triage issues, issue checkup, PR status, close stale issues, issue audit, what can we close, outstanding issues, issue report, cross-reference PRs and issues, repo health check, sprint planning. DO NOT USE FOR: creating issues (use GitHub directly), fixing bugs (use coding skills), or PR code review (use code-review agent).
repository-pro
by Ev3lynx727
"Create professional, well-structured GitHub repositories with industry best practices. Use when: (1) Creating new GitHub repositories, (2) Setting up repository structure, (3) Adding essential files (README, LICENSE, .gitignore), (4) Configuring CI/CD workflows, (5) Setting up contribution guidelines, (6) Adding issue/PR templates, (7) Configuring branch protection rules, (8) Setting description and topics for discoverability, (9) Identifying tech stack and applying appropriate templates (React, Next.js, Django, FastAPI, Go, MERN, T3, etc.)"
frontend-dev
by LadderChaos
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when building web components, pages, dashboards, React components, HTML/CSS layouts, or styling any web UI. Generates creative, polished code that avoids generic AI aesthetics.