Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion jmeridth-skills/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "jmeridth-skills",
"description": "Personal collection of Claude Code skills for git workflow, GitHub Actions, Go development, code review, and productivity.",
"version": "0.1.22",
"version": "0.1.23",
"author": {
"name": "Jason Meridth",
"email": "jmeridth@gmail.com",
Expand Down
1 change: 1 addition & 0 deletions jmeridth-skills/skills/review/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -160,6 +160,7 @@ Apply these to every summary and every comment. This is load-bearing: a review t
- When specific code changes are needed, use GitHub suggestion blocks
- When a suggestion adds or edits a code comment, write it for a reader who never saw the diff. No "now", "instead of", "for now", or "new". Phrase hazards counterfactually ("a mutex here would reintroduce the race", not "reintroduces").
- **Always confirm before approving PRs** unless explicitly told to approve. Asking to see the approval message is not the same as giving the go-ahead.
- **Only request changes for security issues.** Post every other review with the `COMMENT` event, even when it has blocking findings. A change request makes me the blocker. A comment lets the author push updates and lets other maintainers approve and merge.

### Line-level targeting (mandatory)

Expand Down
Loading