Claude Skills by nvie

github.com/nvie

11 skillsA× 112 installs42 views

Liveblocks New Npm PackageAPublish a new placeholder package to NPM under the @liveblocks/* org. Creates a minimal package.json + index.js in a temp dir and gives the user exact commands to run. Use when publishing a brand-new @liveblocks/* package for the first time (version 0.0.0 placeholder to claim the name).toolsgobashVotes: 0GitHub stars: 3
MikadoAMikado method workflow for complex refactorings. Use when the user invokes /mikado, mentions "mikado graph", or wants to break a large code change into safe, incremental steps with automatic revert-on-failure.code-qualitygonodeVotes: 0GitHub stars: 3
Pr ReviewAReview one or more GitHub pull requests as a progressive, understanding-first code review -- start at the highest altitude (what does it do, how, what to grasp before the details) and descend one abstraction layer at a time only when asked. Built for a senior engineer who wants to understand a PR before spending review time on it. Use when the user runs /pr-review with one or more PR links (often a frontend + backend pair), or asks to "review this PR" / "review these PRs". Treats the code dif...code-qualitygoreactVotes: 0GitHub stars: 3
PrAOpen a pre-populated GitHub PR creation page in the browser, with a title and body drafted in nvie's personal writing style. Use when the user runs /pr, or asks to "open a PR", "create a PR", or "draft a PR" for the current branch. This skill never creates the PR itself -- the user reviews and submits it manually.code-qualitygobashVotes: 0GitHub stars: 3
ProperASolve a request strategically and architecturally rather than tactically. Use when the user invokes /proper, asks for "the Proper™ way", wants the long-term design rather than the quickest fix, or wants to refactor / rearchitect first so the requested feature fits naturally. This skill diagnoses why the request feels awkward today, proposes a design change that makes the feature easy, and -- if the strategic path is non-trivial -- hands off to /mikado to execute it in safe incremental steps.businessgorefactoringVotes: 0GitHub stars: 3
Quick ExplainerAPrime the brain for a context switch with one concrete example. Point at a PR, a tech design, a plan, a Mikado graph, an issue, a screenshot, or the current branch, and get back a sub-terminal-window explainer built entirely out of a single worked example: what goes wrong today, and what the same situation looks like once the change lands. Use when the user runs /quick-explainer, or asks to "catch me up on", "remind me what this is about", "what is this PR actually solving", or "explain this ...documentationgonodeVotes: 0GitHub stars: 3
Self ReviewAScrape Claude Code session history to find repeated user corrections, preferences, and contextual guidance, then surface candidates for CLAUDE.md or memory. Use when the user wants to review past sessions for self-improvement, find patterns in their feedback, or bake recurring preferences into persistent configuration.code-qualityrustgoVotes: 0GitHub stars: 3
SlackAWrite a message as a ready-to-paste Slack message, in nvie's own casual voice, using Slack-flavored markdown that formats correctly when pasted into the Slack composer and toggled with cmd+shift+f. Use when the user runs /slack, or asks to "write this as a Slack message", "slackify this", "draft a Slack message", or "post this in Slack". Output is the message text and nothing else -- no preamble, no explanation, no follow-up questions.documentationgodebuggingVotes: 0GitHub stars: 3
Tech DesignADraft, review, pressure-test, compare, and polish technical design documents for product, API, SDK, infrastructure, storage, migration, reliability, security, privacy, performance, data model, or architecture work. Use when an engineer wants to make and defend a technical decision, turn rough notes into a review-ready TD, review an existing TD, compare alternatives, or plan rollout/testing/migration/rollback for a proposed technical change.documentationgotestingVotes: 0GitHub stars: 3
Visually ExplainAProduce a single self-contained interactive HTML document that visually explains how a *specific* system, mechanism, or design in the codebase works -- built for visual learners who find static markdown insufficient. Walks a concrete worked example through its states with toggles, steppers, diffs, and side-by-side comparisons. Invoked explicitly as /visually-explain; it is for explaining a particular thing you can point at in code or a spec, not for general-concept tutorials.designrustgoVotes: 0GitHub stars: 3
Upgrade DepsAUpgrade a Node repo's dependencies in three rounds (patch → minor → major) using npm-check-updates, respecting the project's release-age cooldown. Researches each update's changelog in parallel, bumps the uneventful ones silently, runs the tests, commits, and surfaces only the packages that need a human decision -- a few at a time, most severe first. Works in monorepos (--workspaces, syncpack). Use when the user runs /upgrade-deps, or asks to "upgrade deps", "bump dependencies", "update packa...testingtypescriptgoVotes: 0GitHub stars: 3