gh-first-workflow
Enforce gh-first GitHub investigation, pull request maintenance, and Conventional Commit output rules. Use when investigating GitHub issues or pull requests, creating or updating pull requests, summarizing investigation results, or preparing commit messages.
- License 许可
- Apache-2.0
- 最近更新
- 2026-07-21
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- gh-first-workflow
- metadata
- { "owner": "mryfmo", "scope": "personal", "freshness": "90d", "provenance": "repo=mryfmo/dotfiles; license=MIT", "last-verified": 1784592000000 }
- description
- Enforce gh-first GitHub investigation, pull request maintenance, and Conventional Commit output rules. Use when investigating GitHub issues or pull requests, creating or updating pull requests, summarizing investigation results, or preparing commit messages.
02 资源文件 3
- 参考文档agents/openai.yaml276 B
- 参考文档eval/NOTES.md158 B
- 参考文档references/gh-git-rules.md1.2 KB
03 SKILL.md 正文
GH-First Workflow
Overview
Use this workflow to keep GitHub investigation and commit output consistent with repository policy. For pull requests, keep the description aligned with the full current PR contents, not just the latest delta.
Read Acknowledgement
- After reading this skill, say:
🐙 私は gh-first-workflow を読みました。
Workflow
- Start issue/PR investigation with
ghcommands. - Use
webonly whenghcannot provide required details. - Collect URLs for every issue/PR that was inspected.
- When creating a PR, write the PR description as a summary of the full PR.
- If additional commits are pushed after PR creation, inspect the updated commits/diff with
ghand refresh the PR description so it reflects the full current PR, not only the latest increment. - Include inspected URLs in the response.
- Write commit messages in Conventional Commit format.
Output Checklist
- State that
ghwas used first. - State why
webwas used when fallback was necessary. - Include inspected issue/PR URLs.
- When commits were added after PR creation, confirm the PR description was updated to match the full current PR.
- Keep commit subject in Conventional Commit form:
<type>(<scope>): <summary>. - Do NOT include local absolute file paths (e.g.,
/Users/.../,/home/.../) in any output. Use repository-relative paths instead.
Use gh-git-rules.md for command examples and commit-type guidance.
04 同仓库更多 Skills
shdoc-shell-docs
Write and review shellscript documentation with shdoc annotations. Use when Codex creates, edits, or reviews `.sh` files or shell executables and should add, repair, or normalize `@file`, `@brief`, `@description`, `@arg`, `@option`, and `@example` comments to match shdoc conventions.
python-uv-workflow
Apply Python development policy using uv-first execution, test-first behavior validation, and pre-commit quality gates. Use when implementing or refactoring Python code.
humanizer-ja
AIくさい日本語を、人が書いたように自然でこなれた日本語へ書き換えるスキル。ブログ記事、メモ、メール、文書、SNS投稿、チャット返信などの日本語を書いたり推敲したりするときに使う。AIっぽい言い回しを消したいとき、日本語を自然にしたいとき、言い換えたいとき、硬さを抜きたいとき、トーンを整えたいとき、人間らしい声や温度を足したいときに使う。
gh-comment-attach-files
Attach local files to a GitHub issue or pull request comment via Playwright CLI and return the hosted attachment URLs without submitting the comment. Use when you need GitHub-hosted image or document URLs on github.com or GitHub Enterprise Server.
convert-to-transformers
Use this skill when converting custom PyTorch models to Hugging Face Transformers format. Helps with: (1) Creating PretrainedConfig and PreTrainedModel classes, (2) Writing ImageProcessor/Tokenizer, (3) Compatibility testing, (4) Hub upload preparation. Use when the user wants to make their model compatible with transformers library.
agmsg
Cross-agent messaging via SQLite. Send messages between Claude Code, Codex, Gemini CLI, and other agents. No daemon, no network, no dependencies beyond bash and sqlite3.