Enforce standardized Git branching, commit messages, and pull request templates.
npx skills add https://github.com/7a336e6e/skills --skill git-workflow-7a336e6e
Please help me install this Agent Skill. Skill: git-workflow Source: https://github.com/7a336e6e/skills/tree/main/shared/git-workflow Command: npx skills add https://github.com/7a336e6e/skills --skill git-workflow-7a336e6e
This Skill ensures all code changes are consistently managed through standardized branching, commit messages, and pull request practices, preventing chaos and improving code quality.
frontend/TASK-051-login-form and make commits such as feat(auth): implement login endpoint.Create a new branch for your task by checking out main, pulling the latest changes, and then creating a new branch with the format {agent}/{task-id}-short-description.
High-intent search queries and answers about installing and using this skill.
To standardize Git branch naming, enforce a format like {agent}/{task-id}-short-description for new branches. This structured branching convention prevents chaos and ensures traceability across your development team's version control operations.
The conventional commit format structures atomic commits using clear prefixes like feat(auth): implement login endpoint. This standardized commit message structure creates small, logical version control changes that improve code reviewability and quality.
Creating a structured pull request template involves defining a predefined PR format with effective description sections and review checklists. This standardization enforces consistent submission practices and provides traceability for code review processes.
No specific Git extensions are required to enforce version control workflow standards. The standardization relies on predefined branching conventions, conventional commit message formats, and structured pull request templates applied across standard Git operations.
Use a standardized Git workflow when managing code changes across a development team to prevent chaos. It is needed for consistent version control operations, ensuring atomic commits, clear branching, and structured pull requests for improved code quality.
Structuring commit messages with prefixes like feat or fix enforces conventional commit formats for atomic commits. This practice ensures small, logical version control changes, improving traceability and reviewability across the development team.
Tx1207Create a new project from a template, initialize uv, and configure a local Git repository.
eysenfalkEnforce Git branch naming, commit message formats, and merge policies.
yunaameliaLint and validate Node.js and Python projects with ESLint, TypeScript, Ruff, and MyPy.
KahtafGenerate changelogs from Conventional Commits and manage semantic versioning.