agf-writing-github-issue

Solid

Use whenever a user, product-lead, or qa-engineer wants to create a GitHub issue in the project repo — including phrases like "提一个 issue / 写一个 issue / 报 bug / 把这个开成 issue / gh issue / 上 GitHub / track 一下 / 立个 ticket". Provides the required-field skeleton, locked label set (type / area / epic / priority / severity / phase), gh CLI heredoc template, and the QA-auto-issue exception path. Replaces ad-hoc `gh issue create` calls with inconsistent titles / missing labels / freestyle bodies.

Code & Development 412 stars 14 forks Updated 2 months ago MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
87
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Writing a GitHub Issue Use this skill when any of the following: - 用户说 "写 issue / 提一个 issue / �� bug / 上 GitHub / track 一下 / 立个 ticket" - product-lead 把 PRD 里的 AC 拆成可分派的 issue - dev 在 SIT 自跑中发现 P0 / P1 缺陷（**特殊���径，见下**） - qa-engineer 在 E2E / UAT 中发现 P0 / P1 问题（**特殊路径，见下**） - 主 Claude / 任意 agent 准备调用 `gh issue create` > **拼 body / 写命令前必读** [`references/templates-and-examples.md`](./references/templates-and-examples.md)：Body 模板（feature + bug 增补段）、gh CLI HEREDOC 正确写法、3 个完整例子（feature / bug / dev SIT 自动路径，含 RolexOps 实例需替换为本项目实际值）。 ## 最���输入模式（用户授权 / 2026-05-13） > **默认行为**：用户只给"关键信息"，agent 智能补全其他字段，直接 `gh issue create`，不走草稿 gate。 ### 用户必须给的最少信息 | 信息 | 说明 | |---|---| | **要解决什么 / 想做什么** | 一两句话描述问题或功能想法，bug / feature / chore 可推断 | **就这一条**——其他字段都由 agent 推断 + 补全。 ### Agent 必须自动补全的字段 | 字段 | 推断规则 | |---|---| | **Title** | 按用户描述拟动宾结构 + type prefix `feat(...)` / `fix(...)` / `chore(...)` / `docs(...)`，≤70 char | | **Why / 背景** | 从用户原话扩写 1-2 段；若有相关 PRD / ADR / 历史 issue，主动 grep `docs/prd/` `docs/adr/` 并 cite | | **AC** | 按 feature/bug 套模板生成 2-4 条可验证条件；bug 必含 "修复后用什么验证" | | **type label** | 按关键词判 feat（新功能）/ bug（修缺陷）/ chore（重构/构建/文档）/ adr（架构决策） | | **area label** | grep 用户描述关键词：`frontend`/`React`/`UI`/`组件` → area:frontend；`API`/`endpoint`/`后端`/`数据库`/`migration` → area:backend；`LLM`/`prompt`/`豆包`/`Qwen`/`embedding` → area:ai；`docker`/`compose`/`caddy`/`redis` → area:infra | | **priority** | bug 默认 P1（核心流程影响）；feature 默认 P2（用户说"急/紧急/blocking"→ P1）；data loss / 安全 / 线上挂 → P0 | | **sever...

Details

Author
pcliangx
Repository
pcliangx/AppGenesisForge
Created
5 months ago
Last Updated
2 months ago
Language
Python
License
MIT

Integrates with

Redis · Database FastAPI · Backend

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

backlog

把一条 backlog 创建成 issue（GitHub / GitLab 自动双轨，含三轴 label）—— issue 即单一真源，无本地索引文件

0 Updated 2 days ago
pkulijing
AI & Automation Listed

gh-issue-submit

用 gh CLI 提交高质量 GitHub issue 与 Discussion：模板发现、查重（含已关闭 issue 阅读）、源码调研根因、权限切换陷阱、computer use 回退、提交与验证、正文插图、社区投票（Discussions Poll 能力边界与选型）

2 Updated 1 weeks ago
Linearl
AI & Automation Listed

git-issue-create

Open one standalone GitHub issue with `gh` - duplicate-checked first, conventional title, repo-template-aware body, auto-resolved labels. Use for every issue-filing request no matter how casual: "open an issue", "file a bug", "create issue", "/git-issue-create", "track this", "make a ticket", "raise an issue", "note this down as an issue", "we should fix X later", or whenever the user describes a defect or a wanted capability that is clearly not being built right now. A one-liner ask still counts - this skill owns the whole flow (duplicate search, label resolution, title grammar, body caps), so a raw `gh issue create` skips all of it. Boundary: work starting NOW is not an issue - "let's start X" / "new ticket, begin" goes to `git-branch-create`, and picking up an issue that already exists goes to `git-issue-start`. Breaking one piece of work into a parent plus sub-issues is `git-spec-plan`. Creates the issue immediately without asking for confirmation.

6 Updated yesterday
pivoshenko