pipeliner-create-issue
Research, clarify, draft, create, classify, and verify one implementation-ready GitHub Issue without starting implementation.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- pipeliner-create-issue
- description
- Research, clarify, draft, create, classify, and verify one implementation-ready GitHub Issue without starting implementation.
02 资源文件 1
- 参考文档agents/openai.yaml191 B
03 SKILL.md 正文
Create an Issue
Apply the shared installed repository home and message-only questions contracts. First adoption retains its explicit-target gate. When an answer is needed, ask in the final ordinary message and end the turn immediately; no work or tool calls follow until the Human replies.
Follow Issue-based communication: identify the proposed work by its draft title until GitHub assigns an Issue number, then use that Issue number in status and handoffs. Keep the exact draft-creation approval gate; never predict a number or substitute an existing PR number.
Read AGENTS.md, pipeliner.config.json, the live Project, every relevant open or closed Issue, open pull requests, and implicated repository evidence.
- Determine whether the request is one coherent, independently verifiable outcome. Split unrelated goals and identify duplicates, absorbed scope, dependencies, and already-delivered behavior.
- Resolve material ambiguity from repository evidence. When evidence is insufficient, ask focused questions with tradeoffs and a recommended default only in ordinary messages marked
Question:. Wait indefinitely for required answers without timers or inferred defaults; preserve existing answers. Do not invent product behavior. - Draft an imperative title and complete HTML body using only applicable sections: Summary, Context and evidence, Scope, Acceptance criteria, Verification, Security and privacy, Accessibility, Dependencies, and Out of scope.
- Propose exactly one governed type label, applicable area labels, Status, Priority, Impact, Effort, assignee, and milestone. Default new work to open, unassigned Backlog unless the PM approves a different valid state.
- Show the complete title, body, and metadata before mutation. Put each value the PM needs to copy in its own fenced code block. Require the exact configured Issue-creation approval for that draft.
- Refresh duplicate and Project state immediately before creating. Use
ghto create only the approved Issue, add it to the configured Project, populate fields, and leave the active slot untouched. - Read the Issue and card back. Byte-compare the body and verify title, labels, fields, open state, assignment, Project membership, Backlog status, and absence of an accidental branch or pull request.
Issue creation never authorizes implementation, release, or changes to another Issue.
When release.cycle is configured, follow release scope and phase governance: inspect target/milestone, Release Issue, phase, freeze and blockers without treating phase as Status. Read-only inspection never starts or advances a cycle. Related findings stay on the same Issue; unrelated intake requires exact draft approval.
04 同仓库更多 Skills
pipeliner-work-issue
Use the canonical workflow to start or resume one Issue and lead the next authorized stage.
pipeliner-update
Use the canonical workflow to update an existing Pipeliner adoption while preserving local configuration.
pipeliner-review-issue
Use the canonical workflow to resume review or feedback before or after merge and guide PM Testing.
pipeliner-release-production
Use the canonical workflow to release an approved candidate.
pipeliner-release-candidate
Use the canonical workflow to prepare an exact release candidate.
pipeliner-pipeline-health
Use the canonical workflow to audit pipeline health read-only.