Claude Code Plugins

Community-maintained marketplace

Feedback

gh-task-shaper

@u473t8/learning-app
0
0

Plan and triage work into GitHub issues. Use when Codex needs to decide whether a new issue is required, describe the problem, outline high-level plans and goals, propose architecture, split large work into sub-issues, add labels, and create a GitHub branch for each issue using gh.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name gh-task-shaper
description Plan and triage work into GitHub issues. Use when Codex needs to decide whether a new issue is required, describe the problem, outline high-level plans and goals, propose architecture, split large work into sub-issues, add labels, and create a GitHub branch for each issue using gh.

GitHub Task Shaper

This skill is for planning and triage only. It does not write code or review code. It describes the problem, proposes approaches and architecture, and turns work into well-structured GitHub issues.

Core Principles

  • The planner MUST NOT write code.
  • The planner MUST NOT review or test code.
  • The planner MUST focus on problems, goals, and high-level plans that guide implementation.
  • The planner MUST describe why the problem matters and how it should be solved at the architectural level.

Workflow

  1. Gather context from the current issue or user request.
  2. Decide whether a new issue is needed.
    • If not, update the existing issue with planning details.
  3. If a new issue is needed, create it with a clear, problem-focused title and description.
  4. If the work is large, split into sub-issues:
    • Create a parent issue describing the problem and the need for sub-issues.
    • List sub-issues as a checklist with links.
  5. Classify the issue with labels (tags).
    • If the label taxonomy is unknown, ask for it. Do not invent labels.
  6. Create a GitHub branch for each new issue using the script in this skill.

What to Include in Issue Descriptions

  • Problem: what is broken, missing, or unclear.
  • Impact: why it matters (user impact, risk, or constraints).
  • Goals: what success looks like.
  • Approach: high-level solution and architectural direction.
  • Notes: risks, assumptions, and open questions.

Keep the plan high-level. The description should guide implementation but not include code.

When to Create a New Issue

Create a new issue if any of the following are true:

  • The problem does not fit the scope of the current issue.
  • The work introduces a distinct goal or architectural change.
  • The task is large enough to require independent tracking.

If none of these apply, update the current issue instead.

Using Existing Skills

Use these existing skills when needed:

  • gh-current-issue to get the issue number from the branch.
  • gh-issue-commenter to add planning updates as comments.
  • gh-issue-planner to sync plan sections if the issue already has a plan marker.

Branch Creation

Create a remote branch after creating a new issue:

.codex/skills/gh-task-shaper/scripts/create_issue_branch.sh <issue-number>

Optional flags:

  • --repo <owner/name>
  • --prefix <prefix>

The script returns the created (or existing) branch name.