Loading...
Loading...
Found 237 Skills
Intelligently detects when too many files are staged and automatically groups them by feature or functionality using Conventional Commits with user language preference
Git workflow standards, commit conventions, hooks, and pull request practices. Use this when users need guidance on Conventional Commits, Git hooks with Lefthook, pull request templates, .gitignore configuration, or Git workflow best practices for team collaboration.
Creates Pull Requests for Prowler following the project template and conventions. Trigger: When working on pull request requirements or creation (PR template sections, PR title Conventional Commits check, changelog gate/no-changelog label), or when inspecting PR-related GitHub workflows like conventional-commit.yml, pr-check-changelog.yml, pr-conflict-checker.yml, labeler.yml, or CODEOWNERS.
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team collaboration.
Phase-gated git commit workflow with validation, staging, and CLAUDE.md compliance enforcement. Use when creating commits, staging changes, or when PR workflows need standardized commits. Triggers: "commit changes", "save work", "create commit", or internal skill invocation from PR workflows. Do NOT use for merge commits, rebases, amends, cherry-picks, or emergency rollbacks requiring raw git speed.
Set up `release-please` for automated releases in a repository. Use this skill when the user mentions release-please, `googleapis/release-please-action`, release PRs, conventional commits, `release-please-config.json`, `.release-please-manifest.json`, GitHub Actions release automation, or wants to bootstrap or debug release-please in a new or existing repo.
Creates commits with conventional format and validation. Use when committing changes or generating commit messages.
Create safe Conventional Commit messages and commits from current working tree changes.
Read this skill before making git commits
Create semantic git commits following best practices and Conventional Commits specification.
Git operations guide. Provides how-to for common git tasks. Use when: - Writing commit messages (Conventional Commits format) - Understanding git workflows
A comprehensive Git agent skill combining strategic workflows, strict conventional commit standards, and safe execution protocols. Acts as a senior engineer to guide users through atomic, verifiable, and standardized git operations.