One-click install
npx skills add https://github.com/shoji9x9/skills --skill issue-start-shoji9x9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-start
Source: https://github.com/shoji9x9/skills/tree/main/.agents/skills/issue-start
Command: npx skills add https://github.com/shoji9x9/skills --skill issue-start-shoji9x9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually initiating work from GitHub Issues leads to inconsistent branch naming, missed workflow steps, and non-compliant commit/PR practices across team members.

Core Features & Use Cases

  • Consistent Workflow Standardization: Automates the full process from Issue intake to feature branch creation, implementation, and pull request opening, eliminating manual step variability.
  • Repository-Specific Convention Adherence: Dynamically resolves branch naming, base branch, and commit rules from repository configuration or standard convention documents, with no hardcoded defaults.
  • Phased Execution Control: Supports plan-only, commit-only, or full PR creation modes to match user delegation preferences, avoiding unintended changes.
  • Use Case: For example, when a developer is assigned a GitHub Issue, this skill automatically creates a correctly named feature branch, follows the repository's commit rules, and opens a linked PR when explicitly requested.

Quick Start

Use the issue-start skill to begin work on GitHub Issue 123 and create a linked pull request when you are ready to submit changes.

Frequently Asked Questions about issue-start

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

FAQPage Schema
How do I standardize feature branch creation from GitHub Issues across my development team?

Standardize GitHub Issue-driven development by automating feature branch creation, enforcing repository-specific commit conventions, and dynamically resolving base branches to eliminate manual step variability and ensure consistent workflows.

Can I create a linked pull request automatically when starting work on a GitHub Issue?

Yes, you can create a linked pull request automatically when starting work on a GitHub Issue using the full PR creation execution mode, which handles branch creation and PR generation upon explicit request.

How does repository-specific branch naming convention resolution work without hardcoded defaults?

Repository-specific branch naming convention resolution dynamically reads repository configuration or standard convention documents to determine naming rules and base branches, ensuring compliance without relying on hardcoded defaults.

What is the best way to prevent duplicate feature branches when initiating development from GitHub Issues?

Prevent duplicate feature branches during GitHub Issue-driven development by using automated duplicate branch detection, which checks existing branches before creating a new feature branch for the assigned Issue.

Can I plan the development workflow without automatically committing changes to the feature branch?

Yes, you can plan the development workflow without committing changes by using the plan-only execution mode, which standardizes the initial setup while avoiding unintended commits until explicitly requested.

Does this workflow support dynamic base branch resolution for different repository rules?

Yes, the workflow supports dynamic base branch resolution per repository rules, automatically identifying the correct base branch from repository configuration to ensure pull requests target the appropriate integration branch.