Validate Git branch names against sequential, timestamp, or custom patterns.
npx skills add https://github.com/eavichay/mycli --skill git-validate
Please help me install this Agent Skill. Skill: git-validate Source: https://github.com/eavichay/mycli/tree/main/.cursor/skills/git-validate Command: npx skills add https://github.com/eavichay/mycli --skill git-validate
This skill prevents repository clutter and maintains project traceability by ensuring all feature branches adhere to strict naming conventions and link correctly to specification documentation.
Run the git-validate skill to check if your current branch name complies with the project naming standards and has a linked specification.
High-intent search queries and answers about installing and using this skill.
You can enforce Git branch naming conventions by validating branch names against sequential, timestamp, or custom template patterns to ensure repository consistency and prevent clutter. This process checks the current branch against defined pattern configurations.
Yes, Git branch validation verifies the existence of corresponding specification directories within a spec-kit project structure. It warns the developer if the associated spec directory is missing, ensuring documentation stays synchronized with the feature branch code.
Automating compliance checks for Git branch patterns involves running a validation skill that requires Git CLI access to verify branch names against configured templates. This immediately checks if the branch name follows the required format upon creation.
Yes, you need Git CLI access to validate branch naming standards because the validation process operates within the repository context to verify the current branch name and check for linked specification directories.
Git branch validation supports sequential, timestamp, and custom template patterns for naming enforcement. These patterns ensure that all feature branches adhere to strict naming conventions required by the project configuration.
KamiJeongCreate a numbered git feature branch for Spec Kit projects.
i-standard1Reverse-engineer implemented code into formal requirements definitions mapped in spec-map.yml.
juanca202Automate Git commits after Spec Kit command events.
PiklarValidate Git branch names against sequential or timestamp patterns and check spec directories.
