github/penpot
1
0
Fork 0
mirror of https://github.com/penpot/penpot.git synced 2026-09-17 01:16:13 +00:00
Code Issues Packages Projects Releases Wiki Activity
penpot/.agents/skills/create-issue/SKILL.md
Andrey Antukh fbfef42145 ♻️ Move skills and plans to .agents for cross-tool use 
.agents is the shared home that opencode, Claude Code (through the
.claude/skills symlink) and Codex all read, so the skills and the
saved plans now live there instead of .opencode:

- .opencode/skills moved to .agents/skills (24 files, no content
  changes).
- .opencode/plans moved to .agents/plans; the .gitignore entry
  follows, so plans stay untracked.
- .claude/skills symlink retargeted to ../.agents/skills.
- planner, make-a-plan and review-plan updated to the new plans path;
  new .agents/README.md documents every skill with when-to-use
  examples and links to each SKILL.md.
- workflow/creating-issues memory: create-issue path updated.

opencode discovers .agents/skills natively, so .opencode needs no
reciprocal link.

AI-assisted-by: omen-alpha
2026-09-08 19:40:38 +00:00

1.1 KiB
Raw Blame History

name, description
name description
create-issue 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
  • 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.