jv-vogler
UserPersonal Claude Code skills marketplace
Categories
Indexed Skills (6)
write-description
Use when opening or updating a pull request, writing or fixing a PR description or body, running `gh pr create` or `gh pr edit`, when asked to "write the PR description", or when an existing PR body is stale, a wall of text, or narrates the diff file-by-file.
humanize
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.
architecture
The four-layer frontend architecture — infrastructure → domain → view → routes — with its dependency rules, file layout, naming conventions, and the recurring patterns that hold it together (serialization boundary, initial-data hook ladder, flow state machines, typed domain errors). Use whenever adding or changing a feature, page, API call, hook, form, or component in a React app laid out as src/infrastructure + src/domain + src/view + src/pages; whenever deciding which layer a piece of code belongs in; whenever reviewing a diff for layering violations; and whenever structuring a greenfield React frontend that wants a proven shape. Reach for it even when a request sounds purely local — "add a field to this form", "call this new endpoint", "show a spinner here" — because those are precisely the changes that quietly leak business rules into components.
execute
Execute an implementation plan written by `plan:write` — one named phase, a bounded span of phases, or the whole plan. Use whenever the user asks to execute, implement, continue, or resume a plan or its phases — "run phase 2", "continue the plan", "implement the next phase", "run the whole plan", "go up to phase 4", "execute feature-auth-module-1.md" — or references a plan file in `/plan/`. Runs each phase's tasks under `code:implement`, marks tasks complete in the plan file as they land, and commits each phase on a branch the user chose.
write
Write a new implementation plan file to `/plan/` — phased tasks, explicit requirements, rejected alternatives, and tests — before any code is written. Use when the user asks to plan, spec, or design a new feature, a refactor, a package or framework upgrade, a migration, or an architecture or infrastructure change, and whenever they ask for "a plan" for multi-step work. Produces the plan only; executing it is `plan:execute`.
local-review
Use when reviewing a pull request or branch locally without posting to GitHub — the user says "review PR #N", "review this PR locally", "check this branch's changes", "review my diff", asks whether a PR matches its ticket or does what the task asked, or wants review comments written to a file to read, filter, and copy before publishing anything.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.