Create a GitHub issue and matching branch for development tasks.
npx skills add https://github.com/biz-Stream/bizprint --skill start-task-biz-stream
Please help me install this Agent Skill. Skill: start-task Source: https://github.com/biz-Stream/bizprint/tree/main/.claude/skills/start-task Command: npx skills add https://github.com/biz-Stream/bizprint --skill start-task-biz-stream
Development projects often suffer from unclear work items and inconsistent starting points. This skill provides a standardized workflow to create a task-tracking issue and a corresponding development branch, ensuring everyone starts from the same place.
Create an issue with a clear title and description, then open a relevant feature/bugfix/hotfix branch for the related issue.
High-intent search queries and answers about installing and using this skill.
To create a GitHub issue and branch together, you need a workflow that captures the work item and generates a corresponding branch. This skill creates a GitHub issue with a title and description, then checks out a new branch prefixed with the issue number.
The standard branch naming convention uses specific prefixes like feature/, bugfix/, hotfix/, or chore/ combined with the issue number. This ensures branches are categorized correctly and traceable back to their originating GitHub issue.
To prevent direct commits to main, you need an enforced startup protocol that blocks edits on the main branch. This skill guides contributors to create a tracking issue and checkout a standardized branch before starting implementation.
Yes, you need Git and GitHub CLI installed to automate branch creation from issues. This skill requires both tools to create the GitHub issue and generate the corresponding prefixed development branch automatically.
A standardized workflow for starting development tasks solves the problem of unclear work items and inconsistent starting points. By creating a tracking issue and a corresponding branch, it ensures all contributors begin implementation from the same structured baseline.
The limitation of enforcing branch prefixes is that you are restricted to using feature/, bugfix/, hotfix/, or chore/. Any development task outside these categories will not fit the enforced startup protocol and branch generation rules.
gqf2008Authenticate Hermes Agent with GitHub via gh CLI or git tokens and SSH keys.
mvillmowCreate a GitHub pull request linked to a specified issue.
axone-protocolExecute Rust project quality gates for format, lint, tests, coverage, schema, and docs.
tartinerlabsCreate and validate git branches with enforced naming rules.
