start

Fetch or create a GitHub issue and generate a correctly named branch.

2|Updated May 23, 2026
One-click install
npx skills add https://github.com/psenger/catholic-ai-skills --skill start-psenger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/psenger/catholic-ai-skills/tree/main/.claude/skills/start
Command: npx skills add https://github.com/psenger/catholic-ai-skills --skill start-psenger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetches or creates a GitHub issue and automatically cuts a correctly named branch from main, enabling a clean start to work with guardrails.

Core Features & Use Cases

  • Two invocation modes: EXISTING ISSUE and NEW ISSUE, including automated authentication checks and user identity confirmation.
  • Derives branch names from issue data and enforces conventions (feature/ or fix/ prefixes with 2-4 word slugs) for predictable workflows.
  • Supports reproducible, auditable starts for dev work, incidents, and feature development by linking issues to branches.

Quick Start

Tell the skill to start work on issue #14 or describe the task to open a new issue and create the appropriate branch.

Frequently Asked Questions about start

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically create a GitHub branch from an issue?

You can automatically create a GitHub branch from an issue by using an automation workflow that fetches the issue data and generates a correctly named branch from main. This ensures your development work starts with a clean, linked issue-to-branch structure.

What branch naming conventions should I use for feature development and fixes?

Branch naming conventions for feature development and fixes typically enforce feature/ or fix/ prefixes combined with a concise 2-4 word slug derived from the issue. This generates predictable, auditable branch names linked directly to their originating issues.

Can I start a new GitHub issue and cut a branch at the same time?

Yes, you can start a new GitHub issue and cut a branch simultaneously by describing the task to an automation workflow. The system opens a new issue based on your description and immediately generates the appropriate branch from main.

Does this GitHub workflow automation check user authentication before creating branches?

Yes, this GitHub workflow automation includes automated authentication checks and user identity confirmation before creating branches. This ensures only authenticated users can cut branches, enforcing guardrails for reproducible and auditable development starts.

What is the best way to enforce branch naming conventions across a development team?

The best way to enforce branch naming conventions across a team is to automate the branch creation process from standardized issue data. Deriving branch names directly from GitHub issues enforces consistent prefixes and slugs without relying on manual naming.