feat: add to-issues and to-pr Claude Code skills - #1162
Merged
Conversation
Adds two project skills that write copy-ready GitHub issues and PR descriptions in chat using the repo's templates, in simple English with minimal jargon. Un-ignores .claude/skills/ so shared skills are tracked while local Claude state stays ignored. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds two Claude Code project skills that anyone working in this repo can use:
/to-issues— writes a GitHub issue in chat, ready to copy, using our issue templates (Task, Feature Request, or Bug Report). It picks the right template for what's being described, keeps every heading, and never invents facts — unknown causes become things to investigate./to-pr— writes a PR title and description in chat, ready to copy, using our PR template. It reads the actual diff before writing, links the issue, and only ticks Test Checklist boxes for things that were actually verified.Both skills write in simple English and explain any unavoidable technical term in plain words, so issues and PRs stay readable for translators and partners, not just developers.
Changes
.claude/skills/to-issues/SKILL.md.claude/skills/to-pr/SKILL.md.gitignoreso.claude/skills/is tracked while local Claude state (settings, worktrees) stays ignoredTest Checklist
Skills
/to-issueson a real partner report in a fresh session — it chose the Bug Report template, kept all headings, and produced one copyable block with a plain-English explanation of "Sparkle"/to-pragainst the real change from Task: Pin pnpm version in CI and add build-script approvals (pnpm 12 breaks installs) #1147 in a fresh session — it found the issue number from the commit, mirrored the issue's acceptance criteria, and left unverified checklist items uncheckedGitignore
.claude/settings.local.jsonand.claude/worktrees/are still ignored after the change🤖 Generated with Claude Code