skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
mgratzer/forge66 installs

forge-create-issue

Plan and create well-structured Issues with the user (GitHub, markdown plan/ folder, or other providers), researching the codebase first and confirming the approach and draft interactively. Use when the user or an orchestrating agent asks for forge-create-issue or to file an Issue for work that is already understood, not when a bug merely comes up in conversation; use forge-shape first when the idea is still vague.

How do I install this agent skill?

npx skills add https://github.com/mgratzer/forge --skill forge-create-issue
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill is safe. It provides a structured process for creating and managing GitHub or markdown-based issues. It incorporates codebase research, user clarification, and a mandatory interactive approval step before any actions are taken. All operations use standard Git and GitHub CLI tools in a secure manner.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

  • Runlayerpass

    1/1 file flagged

What does this agent skill do?

Create Issue

Collaboratively plan and create well-structured Issues through interactive discussion. The Issue is created in the project's Issue tracker — see issue-operations for provider detection.

Input

The Issue idea or problem description: $ARGUMENTS

Optional: -- <additional context> for execution guidance.

If no argument is provided, ask the user what they'd like to create an Issue for.

Process

Step 1: Research the Codebase

Explore the relevant code before asking anything: related implementations, integration points, potential reuse, and every place that already makes the decision this work is about. If the work relies on an external dependency, verify it is accessible and flag a broken one before proceeding.

Step 2: Clarify

Use AskUserQuestion to gather what the code can't answer:

  • Problem context — what triggered this, who's affected, current vs desired behavior
  • Success criteria — how will we know this is done
  • Constraints — technical limitations, dependencies

Step 3: Present Alternative Approaches

Skip this step if the input already contains a chosen approach with rationale.

Otherwise, present the structurally distinct approaches you found (usually two to four) rather than a single recommendation; the choice belongs to the user.

For each approach: a one-line summary, how it works, pros and cons, relative complexity (Low / Medium / High), and key files affected. Let the user choose or combine approaches via AskUserQuestion.

Step 4: Assess Scope

Evaluate if this should be one Issue or multiple.

Split when: distinct deliverables, different codebase areas, parallelizable work, or effort exceeds 1-2 days (an estimate for this decision only: the Issue carries no time estimate).

Keep together when: tightly coupled changes or splitting adds coordination overhead.

When splitting, slice vertically — each Issue is a thin end-to-end path (see vertical-slicing). Classify each as AFK or HITL (see afk-vs-hitl.md). Order by dependency, and note which Issues each one is blocked by. A forge-shape breakdown arrives sliced, classified, and ordered: check it against the same rules and re-slice only a horizontal Issue.

If splitting makes sense, offer: an epic with sub-issues (the default for several Issues), linked Issues without a parent, or a single Issue.

Step 5: Draft the Issue

Title: Use conventional commit format — <type>(<scope>): <description>

Labels: Discover what labels exist before applying any — see issue-operations. Apply at least one type label and relevant area labels.

Body structure:

## Summary
[1-2 sentences]

**Execution mode:** [AFK | HITL] <!-- markdown provider: use the `mode` frontmatter field instead -->

## Problem / Motivation
[Why this needs to exist]

## Proposed Solution
[Chosen approach with implementation details]
[The design block, when this adds a module or a variant of something that exists]

### Alternatives Considered
[Other approaches and why they weren't chosen]

### Implementation Constraints
[When applicable: preferred libraries, config locations, patterns to follow, external dependencies]

## Acceptance Criteria
- [ ] [Specific, testable criteria]
- [ ] Tests added/updated
- [ ] [When this replaces or removes something: nothing that existed only for the old one remains, and a check (lint, type, test) fails if it comes back, or why none is possible]
- [ ] Documentation updated (if applicable)

The design block is in deep-modules. When a view explains the Proposed Solution better than prose, include one (see visuals).

Step 6: Review and Create

Present the draft to the user and iterate until satisfied (use AskUserQuestion for approve/revise decisions). Then create the Issue using the project's Issue tracker — see issue-operations for provider-specific mechanics. For several Issues, create them in dependency order, then Link Issues: each sub-issue to its parent, and each Issue to the Issues it is blocked by.

Share the Issue reference. Suggest using forge-implement to start implementation.

Related Skills

Next step: Use forge-implement to implement the Issue.

Example Usage

/forge-create-issue add dark mode support
/forge-create-issue add dark mode support -- keep it to a single Issue
/forge-create-issue

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/mgratzer/forge/forge-create-issue">View forge-create-issue on skillZs</a>