Write GitHub issues, PR descriptions, review comments, and commit messages.
npx skills add https://github.com/SgtPooki/skills --skill github-writing-sgtpooki
Please help me install this Agent Skill. Skill: github-writing Source: https://github.com/SgtPooki/skills/tree/main/skills/github-writing Command: npx skills add https://github.com/SgtPooki/skills --skill github-writing-sgtpooki
High-intent search queries and answers about installing and using this skill.
Start with the core problem in the first sentence, then add Impact, numbered Steps to Reproduce, Expected Behavior, and Actual Behavior. Keep it around 150-250 words, omit empty sections, and link logs or repros instead of pasting them.
Only the What changed section is required: 1-2 sentences explaining the change and why. Add How to verify with reviewer commands and Notes/risks for migrations or behavior changes, targeting roughly 100-200 words total.
Use imperative mood in the subject ("Fix retry starvation", never "Fixed"), keep the subject under 50 characters, and wrap the body at 72 characters. Follow the repo's existing convention, including Conventional Commits only if the repo already uses them.
Split when the source is long or contains multiple findings. Keep the GitHub issue short with root cause, impact, workaround, and next step, and move evidence, logs, and rejected options into a linked secret Gist or Notion memo.
No. It explicitly excludes persistent docs (handled by writing-docs), decision records (writing-spec), and public announcements or release notes (writing-community). It covers only change-oriented GitHub tracker and review text.
xiaoshan1234Extract decisions, owners, and action items from meeting transcripts and notes.
CodingThrustAutomates GitHub Pull Request triage and progression through board statuses.
wimpysworldProvide structured writing rules for clear prose in documentation and content.
zorgentechCreate Architecture Decision Records from pull request metadata and diffs.
