OpenSkillIndex← back to search
claude-codeautomation

Vibe-Skills speckit-taskstoissues

Convert tasks from tasks.md into GitHub issues. Use after task breakdown

install
source · Clone the upstream repo
git clone https://github.com/foryourhealth111-pixel/Vibe-Skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/foryourhealth111-pixel/Vibe-Skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/bundled/skills/speckit-taskstoissues" ~/.claude/skills/foryourhealth111-pixel-vibe-skills-speckit-taskstoissues && rm -rf "$T"
manifest: bundled/skills/speckit-taskstoissues/SKILL.md
tags
#github#issue-creation#task-management#automation#markdown#git
source content

Speckit Taskstoissues Skill

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

  1. Run 
    .specify/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks
    from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").
  2. From the executed script, extract the path to tasks.
  3. Get the Git remote by running:
git config --get remote.origin.url

[!CAUTION] ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL

  1. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.

[!CAUTION] UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL