Loading...
Loading...
Found 319 Skills
Git Commit Rules
Standardized git commits following Conventional Commits. Supports mapping to GitHub and GitLab.
Git operations guide. Provides how-to for common git tasks. Use when: - Writing commit messages (Conventional Commits format) - Understanding git workflows
Quick commit and push with minimal, clean messages
GitLab repository operations. ALWAYS use this skill when user wants to: (1) clone repositories, (2) fork projects, (3) view repo info, (4) create new projects, (5) archive/delete repos, (6) manage repo settings.
Generate appropriate commit messages based on Git diffs
Always apply this skill when committing to git
The human project owner and final authority. Does not write code or run tools -- resolves tie-breaks, approves or denies major decisions, and unblocks deadlocks.
Maintains CHANGELOG.md following Keep a Changelog format and Semantic Versioning. Use when the user mentions preparing or publishing a new release, or asks to review or refactor CHANGELOG.md.
Clean up local branches after PR merges. Syncs main with origin, identifies branches with merged PRs, and proposes safe deletion. Use when the user asks to 'clean up branches', 'delete merged branches', 'sync branches', or mentions branch cleanup.
Advanced git operations including complex rebase strategies, interactive staging, commit surgery, and history manipulation. Use when user needs to perform complex git operations like rewriting history or advanced merging.
⚠️ MANDATORY - YOU MUST invoke this skill before ANY destructive operation. Safety protocol for destructive git/file operations. Lists affected files, warns about data loss, suggests safe alternatives, requires explicit double confirmation. NEVER run destructive commands without invoking this skill.