Agent Skills › penpot/penpot › create-issue

create-issue

GitHub

GitHub Issue 管理技能，支持从PR、草稿或作为子任务创建Issue，以及重命名现有Issue。路由至标准工作流处理标题推导、元数据及模板生成。

.agents/skills/create-issue/SKILL.md penpot/penpot

Trigger Scenarios

需要从PR创建Issue 根据草稿内容创建Issue 创建需关联父级的子Issue 修正模糊或过时的Issue标题

Install

npx skills add penpot/penpot --skill create-issue -g -y

More Options

Non-standard path

npx skills add https://github.com/penpot/penpot/tree/develop/.agents/skills/create-issue -g -y

Use without installing

npx skills use penpot/penpot@create-issue

指定 Agent (Claude Code)

npx skills add penpot/penpot --skill create-issue -a claude-code -g -y

安装 repo 全部 skill

npx skills add penpot/penpot --all -g -y

预览 repo 内 skill

npx skills add penpot/penpot --list

SKILL.md

Frontmatter

{
    "name": "create-issue",
    "slash": true,
    "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.