Standardize Git commits, branch naming, and PR descriptions.
npx skills add https://github.com/dungle-scrubs/agent-config --skill git-dungle-scrubs
Please help me install this Agent Skill. Skill: git Source: https://github.com/dungle-scrubs/agent-config/tree/main/stow/shared/skills/git Command: npx skills add https://github.com/dungle-scrubs/agent-config --skill git-dungle-scrubs
This skill standardizes Git workflows to ensure consistent commits, branch naming, and PR descriptions, reducing ambiguity and improving code reviews.
type(scope): description to convey intent at a glance.feature-, fix-, or docs- to categorize work.node_modules/, .env*, .DS_Store, dist/, build/, *.log, .claude/logs/, *.backup, credentials files).feature-xyz branch, apply conventional commits for each change and include a thorough PR description to facilitate reviews.Apply the git conventions to my current work: format commits using the conventional commits style, name the branch as feature-<topic>, and generate a PR description using the template.
High-intent search queries and answers about installing and using this skill.
To standardize Git workflows, format commit messages using the Conventional Commits style: `type(scope): description`. This structure conveys intent at a glance and reduces ambiguity during code reviews.
The best way to name Git branches for feature development is using kebab-case prefixes like `feature-`, `fix-`, or `docs-`. This categorizes work and ensures predictable branch naming across collaborative projects.
You write a standardized PR description using a structured template that includes Summary, Changes Made, and Testing sections. This ensures thorough documentation and facilitates faster, more predictable code reviews.
You should never stage sensitive or bulky files in Git, such as `node_modules/`, `.env*`, `.DS_Store`, `dist/`, `build/`, `*.log`, `.claude/logs/`, `*.backup`, and credentials files to keep the repository clean and secure.
You need Conventional Commits in collaborative software projects using Git for feature development, bug fixes, and release management. It solves the problem of inconsistent commit histories and improves the predictability of code reviews.
Yes, you can use this Git workflow standardization for bug fixes and release management. It applies Conventional Commits and branch naming rules to ensure consistent documentation and structured PR descriptions across all collaborative development tasks.
gajjalaashok75-UIStages modified files, commits conventionally, and pushes to remote tracking repository.
stanislavjiricekExecute context-aware Git commands with automated commit messages and branch management.
Software-Design-ClubEnforce global coding standards across multi-language repositories during code generation and review.
eysenfalkEnforce Git branch naming, commit message formats, and merge policies.