# Setup Issue

> >-

- **Type:** Skill
- **Install:** `agentstack add skill-jerry0022-dotclaude-setup-issue`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Jerry0022](https://agentstack.voostack.com/s/jerry0022)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Jerry0022](https://github.com/Jerry0022)
- **Source:** https://github.com/Jerry0022/dotclaude/tree/main/plugins/devops/skills/setup-issue

## Install

```sh
agentstack add skill-jerry0022-dotclaude-setup-issue
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Setup Issue — GitHub Issue & Milestone Management

Create issues and milestones with enforced formatting and optional board integration.

## Step 0 — Load Extensions

Check for optional overrides. Use **Glob** to verify each path exists before reading.
Do NOT call Read on files that may not exist — skip missing files silently (no output).

1. Global: `~/.claude/skills/setup-issue/SKILL.md` + `reference.md`
2. Project: `{project}/.claude/skills/setup-issue/SKILL.md` + `reference.md`
3. Merge: project > global > plugin defaults

**Project extensions define:**
- GitHub owner and project board ID
- Additional required labels (e.g., `role:*`, `module:*`)
- GraphQL field IDs for board status/custom fields
- Milestone naming preferences

## Step 1 — Gather details

Determine from user input or ask via AskUserQuestion:
- **Title**: Must follow `[TYPE] Short imperative description` format
- **Type**: bug, feature, refactor, chore, design, docs
- **Description**: Imperative mood, sentence case, no trailing period
- **Target repo** (`{target_repo}`): an `owner/name` slug when the issue belongs
  to a **different** repository than the session's. Absent → the current repo.

If project extension defines additional required fields (roles, modules), ask for those too.

### Target repo — when a caller hands one over

Callers route issues to other repositories: `/claude-learn` files a plugin
defect against the plugin source repo from inside a consumer project, and files
a cross-project learning against that project. **An issue silently created in
the wrong repo is worse than none** — it looks successful, returns a valid URL,
and leaves the real repo untouched.

- Carry `{target_repo}` through to Step 2 as `--repo`, to Step 3's skip
  condition, and to Step 4's check.
- Labels, milestones, and board fields configured for the *current* project do
  not necessarily exist in `{target_repo}`. Verify with
  `gh label list --repo {target_repo}` before sending any label — **including
  `type:*`**: `gh issue create` hard-fails on an unknown label, and a target
  repo that never adopted the `type:` scheme would reject every issue. Missing
  there → create the issue without it and say so, rather than losing the issue.
  Drop milestone/board steps unless the target is configured for them.

## Step 1a — User-value gate (mandatory)

Apply the gate from deep-knowledge/issue-rules.md to EVERY issue before
creating it: implementing this one issue alone must already produce a
positive user effect — direct (feature, visual, bug fixed, fewer crashes)
or indirect (performance, stability, security).

- Fails the gate ("only valuable together with other issues") → do NOT
  create it. Bundle the technical sub-tasks into ONE issue scoped by the
  user value they jointly deliver, sub-tasks as a checklist in the body.
- Multiple issues in one request: gate each one in isolation. If several
  only pass together, propose the merged issue(s) to the user instead of
  creating the originals.
- Milestones may aggregate issues into a larger goal, but never use a
  milestone to justify member issues that fail the gate individually.

## Step 2 — Create the issue

```bash
gh issue create --title "[TYPE] Title" --body "Description" --label "type:X"
```

**With a `{target_repo}` from Step 1, `--repo` is mandatory** — without it `gh`
creates the issue in whatever repo the CWD happens to be:

```bash
gh issue create --repo "{target_repo}" --title "[TYPE] Title" --body "Description" --label "type:X"
```

The body MUST include the user-value line (see deep-knowledge/issue-rules.md):
`**User value:** `

Add optional flags based on project extension:
- `--label "role:Y,module:Z"` — if project defines these label categories
- `--milestone "Name"` — if milestones are configured

## Step 3 — Add to project board (if configured)

Only if the project extension provides owner + project ID — **and the issue
landed in this session's own repository**. Compare `{target_repo}` against the
current repo case-insensitively (same comparison as Step 4.5); equal, or unset,
means the board applies. The board configured here belongs to the current
project, and GitHub happily accepts cross-repo project items, so without this
guard an issue filed into someone else's repository shows up on this project's
board. A `{target_repo}` that merely names the current repo — callers pass the
slug through rather than checking — must not lose its board item.

Add the issue to the project board via the GitHub API.

Set custom fields (e.g., "Agent Role") via GraphQL if field IDs are provided in project extension.

## Step 4 — Verify

Confirm all required parameters are set:
1. User-value gate passed and body contains the `**User value:**` line
2. Labels: at least `type:*` (plus any project-specific requirements) — unless
   Step 1 dropped a label the target repo does not have, which is a reported
   omission, not a failure
3. Milestone: if configured
4. Project board item: if configured **and** Step 3 did not skip it for a
   cross-repo issue

Verify what Steps 1–3 were actually told to produce. A requirement that those
steps deliberately skipped is met, not missing — reporting a successfully
created issue as a hard failure is its own defect.
5. **Landing repo** — when Step 1 set `{target_repo}`, the `owner/name` in the
   returned issue URL MUST match it, **compared case-insensitively** (GitHub
   slugs are case-insensitive, and callers pass through whatever casing their
   metadata carries — a case-sensitive check would fail a correctly filed
   issue). A real mismatch means the issue was created in the wrong repository:
   say so plainly, give the wrong URL, and do not report success. Close the
   misfiled issue only if the user asks.

Missing required items = hard error. Fix before reporting success.

## Milestone Creation

See deep-knowledge/milestone-rules.md for naming conventions and level prefixes.

## Step 5 — Completion Card

After the issue/milestone is created and verified, call
`mcp__plugin_devops_dotclaude-completion__render_completion_card` with variant
`fallback` (no code change, no ship — just a GitHub artifact created).

Pass: `variant: "fallback"`, `summary` (e.g. "Issue #123 created"), `lang`,
`session_id`, and `changes` (issue number → title, labels, milestone).
Output the markdown VERBATIM as the LAST thing in the response.

## Rules

- Every issue passes the user-value gate on its own (deep-knowledge/issue-rules.md) —
  never create file-level/layer-level tasks that only deliver value in combination
- Never use `[FIX]` — bugs are always `[BUG]`
- Always link PRs to issues via `Closes #NNN` in PR body
- Re-evaluate milestone level prefix when issues are added/removed
- Issue status tracking (In Progress / Done) is handled by hooks, not this skill

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Jerry0022](https://github.com/Jerry0022)
- **Source:** [Jerry0022/dotclaude](https://github.com/Jerry0022/dotclaude)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-jerry0022-dotclaude-setup-issue
- Seller: https://agentstack.voostack.com/s/jerry0022
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.