mirror of
https://github.com/penpot/penpot.git
synced 2026-09-19 02:16:14 +00:00
8ff99f0766
Add the verified REST procedure for linking an issue as a sub-issue of an umbrella/EPIC: get the REST id, POST to the parent's sub_issues endpoint with a typed -F field, and verify both directions. Route it from the create-issue skill. AI-assisted-by: deepseek-v4.1-flash
31 lines
1.3 KiB
Markdown
31 lines
1.3 KiB
Markdown
---
|
|
name: create-issue
|
|
description: Create or update GitHub issues (from PR, from draft body, retitle existing). Routes to the canonical flow in `mem:workflow/creating-issues`.
|
|
---
|
|
|
|
# Skill: create-issue
|
|
|
|
Entry point for all GitHub issue work. All rules (title derivation, metadata,
|
|
body templates, Issue Type IDs), all flows, and all `gh` / GraphQL commands
|
|
live in `mem:workflow/creating-issues` (file:
|
|
`.serena/memories/workflow/creating-issues.md`). This skill routes to the
|
|
right flow.
|
|
|
|
## When to Use
|
|
|
|
- **Create from PR** — PR exists; the issue is the changelog/release unit,
|
|
the PR is the implementation. Issue = WHAT, PR = HOW.
|
|
→ memory section **Creating Issues from PRs**
|
|
- **Create from draft body** — Taiga story, user report, discussion; no PR
|
|
yet.
|
|
→ memory section **Creating Issues from Draft Body**
|
|
- **Create as sub-issue** — the issue must be grouped under an umbrella/EPIC
|
|
issue; create it first, then link it to its parent.
|
|
→ memory section **Adding an Issue as a Sub-issue**
|
|
- **Retitle existing issue** — current title is vague, prefixed, or stale.
|
|
→ memory section **Retitling an Existing Issue**
|
|
|
|
Everything else (title derivation, metadata policy, body templates, Issue
|
|
Type IDs, create/verify/cleanup commands) lives in the memory — go to the
|
|
matching section there.
|