skills.rest
glhewett
glhewettCOMMUNITY
Explore all skills by this author →
Website𝕏@greg_hewettGitHub

issues-start

Update issue status, commit changes, and create a feature branch.

Updated Feb 15, 2026
Search Tags:#automation#git#workflow#commit#branching#toml#issue-tracking
One-click install
npx skills add https://github.com/glhewett/public-skills --skill issues-start
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issues-start
Source: https://github.com/glhewett/public-skills/tree/main/issues-start
Command: npx skills add https://github.com/glhewett/public-skills --skill issues-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates manual steps required to begin work on a tracked issue by validating the issue file, updating its status, recording a start comment, committing the change to main, creating a feature branch, and opening a planning context so work can proceed with the issue details in scope.

Core Features & Use Cases

  • Validate and locate issue files: Verifies the presence of .issues/{id}.toml and reads its fields for context.
  • Safe git workflow integration: Ensures the working tree is clean on main, stages and commits the updated issue, and pushes to the remote.
  • Branching and planning: Invokes a subordinate feature-start skill to create a feature branch and enters plan mode with the issue title and comments as requirements.
  • Use Case: When a developer is ready to begin a ticket, use this Skill to mark the ticket in-progress, log the start time and author, push the change, and open a plan context populated with the issue details.

Quick Start

Run the skill with the issue ID (for example, 1 or 0001) to mark it in progress, commit and push the update to main, create the feature branch, and enter plan mode with the issue context.

Frequently Asked Questions about issues-start

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

FAQPage Schema
How do I automate starting work on a tracked issue with git branching?▼

You can automate starting issue work by using a skill that validates a TOML issue file, updates its status to in-progress, logs a start comment, commits the change to main, creates a feature branch, and enters plan mode with the issue context.

How does issue tracking work with TOML files in a git repository?▼

Issue tracking with TOML files stores issue metadata in a `.issues/{id}.toml` file, where fields are edited and comments appended to track progress and context directly within the git repository.

Do I need a clean main branch to create a feature branch for issue work?▼

Yes, a clean main working tree is required to create a feature branch for issue work. The skill verifies the working tree is clean on main before staging, committing, and pushing the updated issue file.

What's the best way to transition an issue to in-progress and enter a planning context?▼

The best way to transition an issue to in-progress and enter a planning context is to run this skill with the issue ID, which updates the TOML status, commits to main, creates a branch, and opens plan mode with the issue details.

Why does updating issue status require committing directly to the main branch?▼

Updating issue status requires committing directly to main so the status change and start comment are immediately pushed to the remote repository before creating the isolated feature branch for development.

Related Skills

Explore More Software Engineering Skills→
glhewettglhewett

issues-create

Create TOML issue files with computed IDs and stage them with git.

Community
Intermediate
bodangrenbodangren
11

issue-executor

Create a feature branch and implementation plan for a GitHub issue.

Community
Intermediate
avvaleavvale

commit

Generate conventional commit messages and run git add, commit, and push.

Official
Basic
glhewettglhewett

issues-plan

Create implementation plans from issue titles and comments in .issues/*.toml files.

Community
Intermediate