- Home
- /
- Categories
- /
- Git & VCS
Git & VCS
Git operations, commit helpers, branch management
bloat-detector
by athola
'Detect codebase bloat through progressive analysis: dead code, duplication,
decisive-action
by athola
Guidance on when to ask clarifying questions vs proceed with standard
project-init
by athola
'Interactive project initialization with git setup, workflows, hooks,
regression-auto-baseline
by jmagly
@.claude/rules/executable-feedback.md - Executable feedback rules
refactor-project
by FradSer
This skill should be used when the user asks for project-wide refactoring, cross-file simplification, consistency standardization across the codebase, duplication reduction, or invokes /refactor-project.
finish-hotfix
by FradSer
This skill should be used when the user asks to "finish a hotfix", "merge hotfix branch", "complete hotfix", "git flow hotfix finish", or wants to finalize a hotfix and merge it into main and develop.
executing-plans
by FradSer
This skill should be used when the user has a completed implementation plan (plan.md) and is ready to execute the tasks defined therein. Actively uses Agent Teams or subagents to execute batches of independent tasks in parallel, following BDD/TDD principles.
create-issues
by FradSer
Create GitHub issues with TDD principles and proper labels
start-feature
by FradSer
This skill should be used when the user asks to "start a feature", "create feature branch", "begin new feature", "git flow feature start", or wants to start working on a new feature branch.
brainstorming
by FradSer
This skill should be used when the user has a new idea, feature request, or ambiguous requirement. It clarifies needs, explores options, and produces a solid design document and BDD specs before implementation starts.
create-pr
by FradSer
Create comprehensive GitHub pull requests with quality validation
quick
by FradSer
Streamlined code review for rapid assessment and targeted feedback. Use when reviewing small PRs, simple changes, or when you need a quick triage to determine if deeper review is required.
commit
by FradSer
This skill should be used when the user requests "commit", "git commit", "create commit", or wants to commit staged/unstaged changes following conventional commits format
zig-docs
by NeverSight
Fetches Zig language and standard library documentation via CLI. Activates when needing Zig API details, std lib function signatures, or language reference content that isn't covered in zig-best-practices.
promptscript
by mrwogu
PromptScript language expert for reading, writing, modifying, and troubleshooting .prs files. Use when working with PromptScript syntax, creating or editing .prs files, adding blocks like @identity, @standards, @restrictions, @shortcuts, @skills, or @agents, configuring promptscript.yaml, resolving compilation errors, understanding inheritance (@inherit) and composition (@use, @extend), or migrating AI instructions to PromptScript. Also use when asked about compilation targets (GitHub Copilot, Claude Code, Cursor, Antigravity, Factory AI).
changelog-generator
by Kilo-Org
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
precommit-setup
by athola
"Configure three-layer pre-commit system with linting, type checking, and testing hooks. Use for quality gate setup and code standards. Skip if pre-commit is optimally configured."
brainstorming
by unclecatvn
"You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation."
issue-auto-sync
by jmagly
MCP tools: Gitea issue management
speckit-taskstoissues
by dceoy
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
canton-network-repos
by NeverSight
Canton Network, DAML, and Splice repository knowledge. Use when working with Canton participants, DAML smart contracts, Splice applications, LF version compatibility, or package ID mismatches. Triggers on Canton, DAML, Splice, decentralized-canton-sync, or LF version queries.
write-freek-dev-blogpost
by freekmurze
"When the user wants to write, draft, or outline a blog post for freek.dev. Also use when the user mentions 'blog post,' 'write a post,' 'freek.dev post,' 'draft a post,' or 'blogpost.' This skill captures the writing style, tone, and structure conventions of freek.dev original posts."
code-review
by unclecatvn
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.
pr-review
by jellydn
Fix PR review comments by implementing requested changes