Generate Werf-conform git branch names from task descriptions and type/scope.
npx skills add https://github.com/werf/werf --skill git-branch-name
Please help me install this Agent Skill. Skill: git-branch-name Source: https://github.com/werf/werf/tree/main/.agents/skills/git-branch-name Command: npx skills add https://github.com/werf/werf --skill git-branch-name
Generates consistent git branch names for new tasks according to Werf conventions, eliminating guesswork and manual formatting.
Provide a task description and desired type/scope; the tool will output a single Werf-compliant branch name.
High-intent search queries and answers about installing and using this skill.
To generate a Werf-compliant git branch name, provide a task description with a desired type and scope. The tool formats the branch as <type>/<scope>/<short-description> and outputs a single valid name.
The correct format for Werf branch naming is <type>/<scope>/<short-description>, using only top-level scopes. The entire branch name must not exceed a maximum length of 50 characters.
No, the Werf branch name generator outputs only the single branch name with no additional text. This ensures the result can be directly copied or used in automated workflows without parsing.
The maximum character limit for a Werf-conform git branch name is 50 characters. The generator enforces this constraint while formatting the type, scope, and short description.
The branch name generator reads its naming rules directly from the CONTRIBUTING.md file, specifically the conventions section. This ensures the output strictly follows the project's established Werf formatting constraints.
dannys-code-cornerDrafts commit titles and optional bodies from diffs using workspace naming conventions.
mhattingpeteStage, commit, and push code changes with conventional commit messages.
as4584Implement GitOps workflows for declarative Kubernetes deployments with ArgoCD and Flux CD.
GaryOcean428Enforce conventional commits, branch naming, Gitflow, and PR hygiene.
