Agent skill · writing content · aiskillstore
git-workflow
Conventional commit format, commit trailers, PR description templates, and git workflow operations (branching, rebasing, merging, stashing, cherry-picking, bisecting, reverting, pushing, pulling). Use whenever the user performs any git operation or invokes any `git` command — including creating commits, writing commit messages, creating or reviewing pull requests, managing branches, rebasing, stashing, cherry-picking, bisecting, or pushing/pulling. Do NOT use for purely conceptual questions about git internals that involve no actual operation.
Why this skill is useful
Codifies commit message standards and PR guidelines that the AI could infer but now doesn't have to guess.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Git Workflow Expert This skill provides guidance on commit standards and PR best practices. 🔧 Commit Standards Conventional Commits Follow the Conventional Commits specification: Commit Types Commit Type Reference Type Description Example ------ ------------- --------- feat New feature Adding user authentication fix Bug fix Fixing null pointer error docs Documentation only Update README style Formatting changes Code formatting, no logic change refactor Code refactoring Restructure without behavior change perf Performance improvement Optimize algorithm test Adding/updating tests Add unit tests build Build system changes Update webpack config ci CI/CD changes Update GitHub Actions chore Maintenance tasks Update dependencies revert Revert previous commit Revert "feat: add feature" Commit Message Guidelines Subject line: Use imperative mood ("add" not "added" or "adds") Don't capitalize first letter No period at the end Maximum 50 characters Body: Wrap at 72 characters Explain what and why, not how Use bullet points for multiple changes Example: Commit Trailers Add metadata to commits using trailers: Example with multiple trailers: 📝 Pull Request Guidelines PR Title Follow the same format as commit messages: Examples: feat(auth): add OAuth2 authentication fix(api): resolve race condition in data sync docs(contributing): update contributor guidelines PR Description Template PR Best Practices 1. Keep PRs small - Easier to review, faster to merge 2. One feature per PR - Don't mix unrelated changes 3. Update documentation - Keep docs in sync with code 4. Add tests - Don't merge without test coverage 5. Respond to reviews - Address feedback promptly 6. Squash commits - Clean up commit history before merge 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/git-workflow--809de8