command-task-start

Lock a GitHub issue, prevent duplicate PRs, and create a branch.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/aroido/vibesmith --skill command-task-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-task-start
Source: https://github.com/aroido/vibesmith/tree/main/.codex/skills/command-task-start
Command: npx skills add https://github.com/aroido/vibesmith --skill command-task-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that when you start working on a GitHub issue, you do so safely by preventing conflicts with other team members and ensuring the issue is ready for development.

Core Features & Use Cases

  • Assignee Lock: Automatically assigns the issue to you to prevent others from picking it up.
  • Duplicate PR Prevention: Checks if an open Pull Request already exists for the issue.
  • Project Status Update: Transitions the issue's status in your GitHub project board to "In progress".
  • Branch Creation: Creates a new Git branch named according to issue details (e.g., frontend/issue-12-fix-login-bug).

Quick Start

Use the command-task-start skill to begin working on GitHub issue number 12.

Frequently Asked Questions about command-task-start

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

FAQPage Schema
How do I safely start working on a GitHub issue without conflicting with other developers?

To safely start a GitHub issue, you can use an assignee lock to claim the issue, check for existing duplicate pull requests, update the project status to 'In progress', and generate a descriptive git branch name.

What is the best way to automate git branch creation from GitHub issue labels?

Automating git branch creation from GitHub issues involves reading issue labels to determine the appropriate branch prefix, then generating a descriptive branch name like 'frontend/issue-12-fix-login-bug' to maintain workflow consistency.

Do I need gh, jq, and rg CLI tools to automate GitHub issue tracking and branching?

Yes, you need the gh, jq, and rg CLI tools installed because they are required for GitHub interaction, JSON data processing, and pattern searching to validate issue tracking data before transitioning project status.

How does an assignee lock prevent duplicate pull requests in GitHub project management?

An assignee lock prevents duplicate pull requests by automatically assigning the GitHub issue to you, signaling to other developers that the issue is claimed, while simultaneously checking if an open pull request already exists.

Can I transition GitHub project board status to 'In progress' automatically when starting an issue?

Yes, you can transition GitHub project board status to 'In progress' automatically by integrating workflow automation that validates the issue's readiness and updates the project tracking board upon branch creation.