菜单
Fetches an existing GitHub issue by number, rewrites it to a structured template with gitmoji title and consistent sections (problem, acceptance criteria, steps to reproduce, technical notes), and updates it in-place via gh issue edit.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generates changelog entries from git history following Keep a Changelog conventions and cuts versioned releases. Use when the user wants to update CHANGELOG.md with recent commits or promote [Unreleased] to a versioned release.
Creates a conventional git commit with gitmoji prefix and lowercase imperative message. Use when the user is ready to commit staged changes or wants help composing a clean, atomic commit message.
Scaffolds production-ready CLI projects from language templates, supporting Go with Cobra, Makefile, golangci-lint, goreleaser, and GitHub Pages docs; and Python with Typer, uv, ruff+mypy, PyPI OIDC trusted publishing, and GitHub Pages docs. Use when the user wants to bootstrap a new command-line tool project from scratch.
Analyzes a codebase and generates LLM-optimized documentation covering project overview, architecture, build system, testing, development patterns, deployment, and a file catalog. Use when the user wants to document a codebase or refresh existing project documentation.
Transforms documents into polished self-contained HTML by reading Markdown/text directly, converting other supported inputs with uvx markitdown, selecting from 20 purpose-built templates, and generating the output.
Turns a rough description into a structured GitHub issue with gitmoji title, problem statement, acceptance criteria, optional interview mode, and posting via gh CLI.
| name | refine-issue |
| description | Fetches an existing GitHub issue by number, rewrites it to a structured template with gitmoji title and consistent sections (problem, acceptance criteria, steps to reproduce, technical notes), and updates it in-place via gh issue edit. |
Fetch a GitHub issue by number and rewrite it to a consistent template. The skill reads the issue, optionally reads the codebase for context, then produces a structured version with a gitmoji-prefixed title, 🎯 Problem, 📋 Description, ✅ Acceptance Criteria, and more. Shows a before/after diff before updating.
gh issue view --jsongit ls-files + key files) to enrich Technical Notes and validate acceptance criteria/create-issue: gitmoji title, 🎯 Problem, 📋 Description, ✅ Acceptance Criteria, 🔁 Steps to Reproduce (bugs), 💡 Technical Notes--dry-run prints the gh issue edit command without executing itgh issue edit/refine-issue <number> # fetch, rewrite, confirm, update
/refine-issue <number> --repo owner/repo
/refine-issue <number> --dry-run # show rewritten issue without posting
| Type | Gitmoji | Example title |
|---|---|---|
| feat | ✨ | ✨ add oauth login via google |
| bug | 🐛 | 🐛 password reset link expires too early |
| chore | 🔧 | 🔧 upgrade go to 1.23 |
| refactor | ♻️ | ♻️ simplify auth middleware |
| perf | ⚡️ | ⚡️ cache user profile queries |
| docs | 📝 | 📝 document deployment steps |
| test | 🧪 | 🧪 add integration tests for login flow |
| security | 🔒 | 🔒 sanitize file upload paths |
| ui | 💄 | 💄 update button styles to match design system |
## 🎯 Problem
<one paragraph — why this matters, what pain it addresses>
## 📋 Description
<what needs to be done>
## ✅ Acceptance Criteria
- [ ] <criterion 1>
- [ ] <criterion 2>
## 🔁 Steps to Reproduce
> Only included for bug issues
1. <step 1>
2. <step 2>
- **Expected:** <what should happen>
- **Actual:** <what happens instead>
## 💡 Technical Notes
> Optional — file paths, APIs, related code, implementation hints
parse args: require <number>; extract --repo, --dry-run
fetch issue:
gh issue view <number> --json title,body,labels,state [--repo owner/repo]
gh error and stopread codebase context:
git ls-files to see the file structureanalyze existing content:
/create-issue)rewrite:
show diff: print old title + body, then new title + body, and ask:
Update issue #<n> with this rewrite? [yes / edit / cancel]
post:
gh issue edit <number> \
--title "<gitmoji> <title>" \
--body "<body>" \
[--repo <owner/repo>]
--dry-run: print the command above without running itreport: print the issue URL
gh issue edit without user approval- [ ] task itemsgit ls-files + 1–2 files max; this is context, not a full code review