菜单
Create GitHub issues and pull requests using the GitHub CLI (gh). Always write the body to a file in .tmp/ and pass it via --body-file so descriptions are descriptive and consistent.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/dvcrn/skills --skill gh命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Install and configure PostHog in an Elixir/Phoenix project, including backend SDK, runtime configuration, an app-owned analytics boundary, identity wiring, JS client assets, template wiring, Plug middleware, and verification. Use when adding PostHog analytics or event capture to an Elixir or Phoenix application.
Install and configure Sentry in an Elixir or Phoenix project using official modern defaults, including runtime DSN configuration, Sentry.LoggerHandler with log message capture and rate limiting, Sentry.PlugContext placement, Cowboy/Bandit server detection, Oban error reporting, PII scrubbing, source code packaging for releases, and verification. Use when adding Sentry error monitoring or updating Sentry setup in an Elixir codebase.
SwiftUI state management using @Observable Store containers (Observation framework, iOS 17+), @Environment injection, store composition, derived state, and async mutation patterns. Use when designing or reviewing Store architecture, migrating from ObservableObject/Combine, translating React hooks or React Query patterns to SwiftUI, or implementing shared app-wide state containers.
正在显示 SKILL.md
| name | gh |
| description | Create GitHub issues and pull requests using the GitHub CLI (gh). Always write the body to a file in .tmp/ and pass it via --body-file so descriptions are descriptive and consistent. |
When creating issues or pull requests, always write the body to a file under .tmp/ first, then pass it to gh via --body-file.
Why:
Both commands support reading body from a file:
gh pr create --body-file <file> (or -F <file>)gh issue create --body-file <file> (or -F <file>)--body-file - reads from stdin, but prefer an actual file in .tmp/.
The body must be descriptive and include:
Fixes #123, Refs #456)A good default structure:
## Summary
- …
## Why
- …
## Testing
- …
## Related
- Fixes #123
- Refs #456
!gh pr create --help
.tmp/ exists.--title and --body-file.Example:
mkdir -p .tmp
body_file=".tmp/pr-body-$(date +%Y%m%d-%H%M%S).md"
cat > "$body_file" <<'EOF'
## Summary
- ...
## Why
- ...
## Testing
- ...
## Related
- Refs #123
EOF
gh pr create \
--title "..." \
--body-file "$body_file"
Helpful flags:
--base <branch> to target a non-default base branch--draft for draft PRs--reviewer <user-or-team> to request review--assignee @me to assign yourself!gh issue create --help
Example:
mkdir -p .tmp
body_file=".tmp/issue-body-$(date +%Y%m%d-%H%M%S).md"
cat > "$body_file" <<'EOF'
## Problem
- ...
## Context
- ...
## Proposed fix
- ...
## Related
- Refs #123
EOF
gh issue create \
--title "..." \
--body-file "$body_file"
Before running gh ... create:
.tmp/