Personal Claude Code skills.
Processes and acts on review comments left on a GitHub PR.
Invoke with a PR URL or number:
/process-pr-review https://github.com/owner/repo/pull/123
/process-pr-review 123
What it does:
- Fetches all unresolved review threads via the GitHub GraphQL API
- Assesses each comment and proposes an action (fix, refactor, or dismiss with reasoning)
- After your approval, makes code changes, runs tests, commits, and resolves threads
- Optionally pushes to the remote
Requirements: gh CLI, authenticated with repo access.
Resolves Git merge conflicts by triaging first — mechanical files and structurally-obvious hunks get resolved instantly, and only genuinely ambiguous or contradictory changes get deep investigation and a question.
Triggers automatically when conflict markers appear, or invoke explicitly:
/solve-merge-conflicts
What it does:
- Orients once (
git status+ enablesgit rerere), not with a battery of commands per file - Buckets every conflicted file up front — lock/generated files are regenerated with no reasoning, migration-number collisions get one batched question, everything else becomes a "content conflict"
- Runs
mergiraf(if installed) on the remaining content conflicts — a syntax-aware merge tool that resolves structurally-independent hunks without any intent-reasoning at all - For whatever's still conflicted, reads the hunk and pulls git history only on demand, then auto-resolves additive conflicts (imports, config keys, tests) and asks — in one batched turn, not one question at a time — about anything genuinely contradictory
- Validates at the scope of the change, using the project's own check commands where documented, before completing the merge, rebase, or cherry-pick
- Reports a compact summary: how many files were mechanical, auto-merged, or asked about
Requirements: git with a repository that has active conflict markers or a pending
merge/rebase/cherry-pick operation. mergiraf is optional but recommended.
Explains where the conversation stands when you've lost the thread — too technical, too deep, or too long. Does no new work; it hands control back to you.
Triggers on "ik ben de draad kwijt", "leg dit simpel uit", "wat wordt er van mij gevraagd", or invoke explicitly:
/noob
/noob wat is een migration
What it does: answers in four fixed blocks, in your own language, under ~250 words — what we're working on, where we stand, what just happened (jargon-free), and what it needs from you, with the options and a recommendation.
Requirements: none. No tool calls, no file access — it reads only the conversation.
Uses npx skills — the open agent skills CLI.
npx skills add madebybob/skills/code -a claude-code # code skills
npx skills add madebybob/skills/general -a claude-code # general skillsTo install non-interactively:
npx skills add madebybob/skills/code -a claude-code -y
npx skills add madebybob/skills/general -a claude-code -ySkills are available immediately in new Claude Code sessions. Invoke them with /skill-name.