VdustR
- 39 skills
- 0 followers
- 1 repo stars
- 2 months ago last updated
- ▌ Vp Git · vdustr bundleHandle personal Git and GitHub workflows, including commits, repository setup, gitignore files, cleanup, and pull request lifecycle decisions. Use for Git changes that need safety, repository conventions, or host-aware evidence. Boundary: use vp-stacked-pr for stacks of dependent PRs or branches, and the specialized PR skills for briefing, checklist verification, review follow-up, or comment resolution.
- ▌ Vp Tldr · vdustr bundleWrite or rewrite the concise summary that opens an artifact, message, or update so a reader without prior context can quickly understand the outcome, relevance, current state, and required action. Use for TL;DR blocks, executive summaries, pull request or issue openings, design documents, investigations, handoff notes, status updates, and other content whose conclusion or important uncertainty is buried. Boundary: covers the summary only, not the surrounding body and not a review of the underlying work.
- ▌ Vp Retro · vdustr bundleReflect on a recent agent session to find evidence-backed improvements to collaboration, instructions, skills, or workflow. Boundary: not a code or PR review.
- ▌ Vp Cspell · vdustr bundleDiagnose and fix cspell unknown-word findings or bootstrap repository cspell configuration. Boundary: not for other spell checkers or general lint errors.
- ▌ Vp Github · vdustr bundleWork with GitHub platform behavior that is not a Git operation: attaching images, videos, or files to issues, pull requests, and comments; controlling how Markdown renders on GitHub surfaces; and choosing a credential that can reach the endpoint. Use for any request to upload, attach, embed, or show a local artifact on GitHub. Also use proactively when writing or editing GitHub content and an available screenshot, recording, diagram, or other local file would provide material evidence, even when the user did not say "upload." Boundary: use vp-git for local Git work, vp-stacked-pr for stacks, and the vp-pr-* skills for review workflows.
- ▌ Vp Skills · vdustr bundleManage agent skills with the npx skills CLI: discover, inspect, install, update, remove, verify, or repair skill installations. Boundary: not for authoring skill content.
- ▌ Vp Autodev · vdustr bundleTake a valid issue or development task through research, reproduction, solution design, implementation, verification, draft PR review, feedback loops, merge, and release follow-up. Use for end-to-end development in repositories the user owns or is authorized to change. Boundary: use a narrower dependency, reproduction, checklist, or PR skill when the request covers only that step. In a user-specified repository the user owns, this workflow owns delivery through merge and required release follow-up when the repository's rules permit it and the change is low risk and fully verified. It does not authorize unrelated fixes or writes outside that workflow.
- ▌ Vp Prename · vdustr bundleGenerate a concise, meaningful title for the current session based on its overall theme. Boundary: not for files, variables, branches, or other names.
- ▌ Vp Recording · vdustr bundleCapture software as a file: a still screenshot of a running interface, a scripted browser walkthrough with a visible cursor and subtitles, a frame-accurate render of generated or mathematical motion, or a macOS window capture. Use for screenshots, before-and-after images, demo videos, screencasts, walkthroughs, animated GIFs, a bug reproduction that has to be delivered as an image or a video, and any request to record, film, screenshot, or show what an interface is doing, including a UI behind a login. Every path ends at a file on disk. The browser paths, still and video, and the render path are cross-platform, though a still behind a login needs a display; capturing a native window, still or video, is macOS only. Boundary: use vp-minimal-repro for a re-runnable reproduction that needs no image, and vp-github to attach the result to an issue or pull request.
- ▌ Vp Stacked Pr · vdustr bundleBuild, submit, merge, and repair stacks of dependent pull requests, merge requests, or branches. Use when a change is split across layers that each depend on the one below, when a dependent branch broke after its parent merged, or when choosing between GitHub's native stacks and a manual rebase. Platform automation exists on GitHub only; the manual repair path is plain Git and works on GitLab, Gitea, or any other host. Boundary: use vp-git for single-branch commits, cleanup, and ordinary PR lifecycle work.
- ▌ Vp Env Secrets · vdustr bundleSafely inspect, select, stage, persist, or load sensitive environment variables from dotenv files using dotenvx. Use for API keys, tokens, credentials, local secret files, or commands that need those values.
- ▌ Vp Pr Briefing · vdustr bundleOrient a user to an unfamiliar GitHub pull request. Use when taking over, summarizing, or understanding a PR, its implementation, review state, risks, and next actions. Boundary: not for resolving feedback or writing a review.
- ▌ Vp Deps Migrate · vdustr bundleReplace a library or migrate deprecated API patterns. Use when switching dependencies, frameworks, build tools, or APIs. Boundary: use vp-deps-upgrade for a version change within the same dependency.
- ▌ Vp Deps Upgrade · vdustr bundleUpgrade dependencies with breaking-change and compatibility analysis. Use for version bumps, outdated packages, security updates, and dependency-bot PRs. Boundary: use vp-deps-migrate when replacing a library or API family.
- ▌ Vp Guided Focus · vdustr bundleGuide requirement clarification before planning complex work. Use when the user asks to focus, align, or answer questions first. When considering it proactively, ask before activating. Boundary: skip for clear, low-risk tasks.
- ▌ Vp Minimal Repro · vdustr bundleReduce an observed failure to a small reproduction that fails on demand and passes once the cause is removed. Use when a failure has been seen and the next step would otherwise be to drive the whole system again to watch it, or when a reproduction has to be rebuilt standalone to demonstrate or share it. Applies at any layer, including build tools, libraries, services, runtimes, and version-specific behavior. Boundary: starts from an observed failure and ends at a re-runnable reproduction; not for filing the report or deciding where it goes.
- ▌ Vp Session Wrapup · vdustr bundleClose out an agent session: summarize the outcome and open items, then find leftover state such as scratch files, uncommitted or unpushed Git work, running services, staged secrets, and temporary configuration. Use when the user ends, wraps up, hands off, or archives a session, including a conditional request to clean up whatever carries no risk. Boundary: use vp-retro for workflow improvement analysis.
- ▌ Vp Checklist Runner · vdustr bundleVerify and update checklist items in GitHub PRs or issues. Use when asked to run, verify, or check off an existing checklist. Boundary: not for authoring a checklist or resolving review comments.
- ▌ Vp Issue Investigator · vdustr bundleInvestigate a suspected software problem, decide whether it is real and still relevant, find related issues, and prepare or file an evidence-backed issue. Use for findings from repository scans, bug reports, regressions, or problems discovered during development. Boundary: establishes and records the problem; use an implementation workflow to fix it.
- ▌ Vp Pr Review Followup · vdustr bundleFollow up on GitHub PR conversations from the reviewer side. Use to verify author replies or fixes, challenge unsupported responses, remind authors, or resolve threads opened by the reviewer. Boundary: authors addressing feedback should use vp-pr-comment-resolver.
- ▌ Vp Pr Comment Resolver · vdustr bundleProcess author-side GitHub PR feedback: verify comments, make focused fixes, reply through the supported mechanism, and resolve eligible threads. Use for actionable submitted-review bodies, unresolved pull request review comments (inline code comments), or actionable issue comments in the PR conversation. Boundary: not for writing reviews or verifying checklists.
- ▌ Vp Agent Browser Session · vdustr bundleManage persistent, login-required agent-browser sessions and dedicated Chrome profiles. Use to select installed or CLI-bundled agent-browser guidance, create, reuse, migrate, inspect, or delete managed profiles, and run agent-browser with a stable worktree-scoped session. Boundary: never attach to the user's daily Chrome profile or inspect sensitive browser stores.
- ▌ Vp Macos Clean Uninstall · vdustr bundleResearch, plan, and perform a clean macOS application or CLI uninstall, including optional residue review. Boundary: macOS only; do not remove SIP-protected system components or unrelated browser data.
- ▌ Vp Long Running Processes · vdustr bundleSafely reuse, start, inspect, stop, or restart persistent processes such as servers, watchers, browsers, and background agents. Boundary: not for one-shot commands that naturally exit.
- ▌ Vp Typescript Best Practices · vdustr bundleGuide TypeScript implementation, review, refactoring, error fixes, runtime validation, and type-level API design in .ts, .tsx, and .test-d.ts files.
- ▌ Vp Foreign Agent Skill Loader · vdustr bundleTemporarily reuse repository-local skills written for another agent system. Use only when the user explicitly asks to scan or load foreign skill roots without converting them into native skills.
- ▌ Retro · vdustr bundleSession retrospective — review recent work to discover improvement opportunities through interactive dialogue. Analyzes corrections, undocumented practices, efficiency patterns, tool usage, and workflow gaps. Use when the user wants to reflect on recent work and find ways to improve their AI collaboration workflow. Common moments: end of session, after a PR, after debugging, after a code review, after finishing a major task, or whenever something felt inefficient. Use when asked to "retro", "session retro", "session review", "review this session", "what can I improve", "retrospective", "what went wrong", "how can I be more efficient", or when the user wants to improve their CLAUDE.md, discover useful skills, optimize existing skills, or design new workflows based on recent patterns. Boundary: not for code review, not for PR review (use pr-review-toolkit).
- ▌ Cspell · vdustr bundleHandle cspell unknown word warnings with a prioritized decision tree and config bootstrapping. Use when users encounter cspell diagnostics, spelling errors from cspell, CI or linting failures on unrecognized words, or ask to add words to the cspell dictionary, suppress cspell warnings, or choose between cspell:words and cspell:ignore directives. Also trigger when setting up cspell in a new project, when any cspell-related IDE warning appears, or when a pre-commit hook fails due to unknown words. Boundary: not for non-cspell spell checkers (typo, codespell, Vale, textlint) or other linting tools (ESLint, markdownlint).
- ▌ Skills · vdustrManage agent skills using the npx skills CLI. Use when the user asks to "install a skill", "add a skill", "remove a skill", "list skills", "update skills", "find skills", "search for skills", or mentions "npx skills", skill management, or agent skill installation. Also trigger when the user mentions skills.sh, agent-skills, vercel skills, or wants to discover available skills for their environment. Boundary: not for creating new skills (use skill-creator) or managing plugins (/plugin commands).
- ▌ Prename · vdustrGenerate a meaningful session name based on the overall session theme, not just the last action. Use when asked to "name this session", "rename session", "prename", "give this session a name", "what should I call this session", or when the user invokes /prename. Outputs a concise session title, with a platform-specific rename command only when the current agent supports one. Boundary: not for renaming files, variables, or git branches.
- ▌ Deps Migrate · vdustr bundleReplace one library with another (e.g., moment.js to date-fns, webpack to vite), or migrate deprecated API patterns within the same library (e.g., React 19 forwardRef removal, Vue 3 Options API to Composition API). Use when asked to "replace X with Y", "migrate from X to Y", "switch from X to Y", "swap X for Y", "convert from X to Y", "port from X to Y", "remove deprecated forwardRef", "migrate to new API", or when planning library replacement or API migration. Also trigger when the user mentions switching libraries, finding alternatives, or removing deprecated patterns. Boundary: for replacing libraries or migrating API patterns. Use deps-upgrade for version bumps within the same library.
- ▌ Deps Upgrade · vdustr bundleUpgrade dependencies with breaking change detection and migration planning. Use when asked to "upgrade dependencies", "update packages", "bump dependencies", "bump <package> to <version>", "update <package> to version <version>", "handle dependabot PR", "handle renovate PR", "check for breaking changes", "upgrade <package> to <version>", "check outdated dependencies", "scan for updates", or when reviewing dependency bot PRs (dependabot, renovate, GitHub Actions), or when addressing security alerts, CVE notices, or vulnerability patches. Also trigger when the user mentions outdated packages, version bumps, or package manager update commands. Boundary: for version bumps within the same library. Use deps-migrate when replacing one library with another.
- ▌ Guided Focus · vdustrGuided focus questioning to align on requirements before planning or complex tasks. Use when asked to "focus first", "ask me questions before planning", "guided focus", "help me clarify requirements", "let's align before starting", or proactively when detecting complex/ambiguous tasks that would benefit from requirement clarification before entering plan mode or execution. Always ask the user whether to activate before starting proactively. Boundary: not for simple, unambiguous tasks with clear requirements.
- ▌ Checklist Runner · vdustr bundleParse and verify checklists from GitHub PRs and issues, auto-checking items that pass verification. Use when asked to verify PR/issue checklists, check off items, process checklist tasks, run the checklist, or when a PR/issue contains unchecked checkbox items that need verification. Also trigger when the user mentions "checklist", "checkbox", or wants to auto-verify PR merge requirements. Boundary: not for creating new checklists (just write markdown) or handling PR review comments (use pr-comment-resolver).
- ▌ Gitignore Builder · vdustr bundleBuild and merge .gitignore files using github/gitignore templates with smart project detection. Use when the user asks to "create gitignore", "build .gitignore", "add gitignore templates", "set up gitignore", "update gitignore", or requests "/gitignore". Also trigger when observing projects without .gitignore, seeing untracked files like node_modules/, .env, __pycache__/, or *.log in git status, or after git init in a new repo. Boundary: not for .dockerignore or other non-git ignore files.
- ▌ Stacked Pr Rebase · vdustr bundleRebase stacked PRs after parent PR is merged, preserving only your commits. Use when the user asks to "rebase my PR after parent merged", "update stacked PR", "fix PR after dependency merged", "cherry-pick my commits to new base", "sync stacked PR", or when a PR contains commits from a merged parent PR that need to be removed. Also trigger when the user mentions stacked PRs, dependent PRs, PR chains, or parent PR merges affecting their branch. Boundary: not for regular rebases onto main or resolving merge conflicts in non-stacked PRs.
- ▌ Pr Comment Resolver · vdustr bundleAutomate PR comment review, fix, and resolution workflow with atomic commits. Use when the user asks to "handle PR comments", "resolve PR review comments", "fix PR feedback", "process review comments", "address PR suggestions", "deal with review comments", or provides a GitHub PR URL with review comments. Also trigger when the user mentions unresolved PR threads or wants to batch-process reviewer feedback. Boundary: not for writing PR reviews (use code-review) or PR checklists (use checklist-runner).
- ▌ Macos Clean Uninstall · vdustrCleanly uninstall applications on macOS with thorough research and cleanup. Use when the user asks to "uninstall", "remove", "delete", or "clean up" an application, program, CLI tool, or package on macOS. Also trigger when the user wants to check what residual data an app has left behind, asks to "check leftover files", or mentions cleaning up after an app removal. Boundary: macOS only. Not for Linux/Windows, removing SIP-protected system apps, or clearing browser data.
- ▌ Typescript Best Practices · vdustr bundleTypeScript coding guidelines with dos and don'ts for type design and patterns. Use when writing, reviewing, or refactoring TypeScript code in projects with tsconfig.json or .ts/.tsx files. Trigger when the user asks to "review TypeScript code", "check my TS code", "write TypeScript", or when creating or modifying any .ts/.tsx file. Also applies when discussing type design, generics, naming conventions, interface vs type decisions, or TypeScript patterns. Boundary: not for JavaScript-only projects without TypeScript configuration.