Audit a repo for names and defaults tied to one person's setup — home paths, personal channels, dated tags, OS-only commands, stale repo names. Use when preparing a project for reuse.
Skills in this repository
laurigates/claude-plugins - Page 2
SkillsMP has collected 476 skills from laurigates/claude-plugins. Open a skill to review its source and details.
laurigates/claude-pluginsShowing 40 of 476 collected skills.
Full Blueprint Development setup in one pass - PRD-derived rules, workflow commands, manifest mapping. Use when bootstrapping rules and commands together; for rules alone use blueprint-generate-rules.
(Re)generate path-scoped rules from PRDs into generated_rules_path, with hash-based conflict checks. Use when creating or refreshing rules from docs/prds/; for full setup use blueprint-development.
Install and configure dead-code tooling (Knip, Vulture, cargo-machete, deadcode): config, pre-commit, CI. Use when setting up or migrating unused-code scanning; to run a scan use code-dead-code.
One-pass GitHub Actions cost report for an org or repo: billing, per-workflow runs and durations, waste counts. Use when investigating CI/CD costs; to fix one repo's waste use finops-waste.
Branch names: type prefix (feat/, fix/, chore/), issue number, kebab-case. Use when picking a name for a new branch or setting a repo's branch-naming convention.
Machine-readable git output for scripts: status --porcelain=v2, diff --numstat, log --format placeholders, ahead/behind counts. Use when a script or agent parses git state, not to make a commit.
Local commits only: stage the changes, write a conventional message, run pre-commit, create the commit. Use when the user says "commit", "save my work", or "stage and commit". Pushing is git-push.
Commit trailer lines: BREAKING CHANGE, Release-As, Co-authored-by, Signed-off-by, parsed with git interpret-trailers. Use when adding, auditing, or parsing trailers in a commit message.
Commit-message and staging conventions: type(scope): subject, logical grouping, explicit-path staging. Reference only, makes no commit. Use when deciding how to word a message or split changes.
Existing commits only: push them to the remote with upstream tracking and --force-with-lease. Use when the user says "push", "send to remote", or "update remote". Commits nothing.
Fixes/Closes/Refs keywords for a change: match the staged diff against open issues by path, label and title. Use when deciding which issue a change closes before its message is written.
Diagnose and fix Claude Code plugin registry corruption — orphaned entries, stale keys, scope conflicts. Use when seeing plugin-already-installed errors or registry drift.
Find and create supporting scripts for plugin skills. Use when auditing skills for script opportunities, improving token efficiency, or extracting bash blocks from SKILL.md.
Traps in GitHub's merge machinery. Use when merging a PR, merging a stacked or serial PR chain, auditing whether a branch really landed, or merging over red CI.
This session's durable learnings, each routed to one home: a rule, recipe, local skill, or plugin PR. Use when a session taught something worth keeping, or asked to distill or codify it.
Tool results that mean something other than they look — a pattern that never compiled, a glob that cannot match a directory, one tier searched but reported absent, a rejected flag reading as "no results". Use when an empty result is about to gate an action,…
Verify code facts by running code, not grepping: is a function really called, is a derived table stale, did a scripted edit write. Use when auditing reachability or batch-editing source.
Keep figures in docs true: cite the command, not a count that moves; scope measurements; fix a corrected claim in every summary. Use when writing a number into docs or correcting a finding.
Check a benchmark, A/B or eval metric measures what it claims: control arms, oracles that can fail, pooled correlations, small x/N. Use when setting up an experiment or a metric says improved.
cargo-dist (dist) release binaries for a Rust CLI. Use when setting up dist-workspace.toml, pairing dist with release-please, or publishing a Homebrew formula.
Installable Rust CLI: embedded default config, config layers, user dirs, clap input beside subcommands. Use when making a binary run outside its repo.
Upgrade blueprint structure to the latest format version. Use when migrating between format versions, enabling monorepo workspaces, or batch upgrading repos.
Benchmark control hazards: mutated controls, disagreeing harnesses, VM lock scaling, hyperfine 2.0 exports. Use when benchmarking, comparing timings, A/B runs, hyperfine.
Read an issue's full comment thread and re-verify its cited evidence at HEAD. Use when scoping a PR or plan from a GitHub issue, or before filing or reversing one in your own tracker.
gh CLI commands with JSON output for agents. Use when querying PRs, issues, runs, or repo metadata; inspecting PR checks; fetching failed CI logs; or mapping a github.com URL to an API call.
Verify a repo's work survives deletion — remote, unpushed commits, stashes — then offer a push or tar backup. Use when asked to rm -rf, delete, or prune a git checkout.
Check upstream HEAD before patching vendored, tarball-installed, or forked code. Use when patching a dependency, custom node, or fork you don't own.
Stop hand edits to release-please files (CHANGELOG, versions) and committed artifacts built from them. Use when editing changelogs, bumping versions, releasing, or feeding a version to generated docs.
Share one CARGO_TARGET_DIR across parallel git-worktree agents so Rust deps compile once. Use when worktrees run cargo concurrently, rebuild deps N times, or fill disk with N target/ copies.
mockito HTTP mocking in Rust tests: expectations, match order, polling clients vs instant mock servers. Use when mocking an HTTP API, a matched() wait loop hangs, or tests hang under concurrent load.
Obsidian Publish and Sync operations. Use when publishing notes, managing change sets, pausing/resuming sync, or recovering sync-deleted files.
Obsidian vault file ops via CLI: read, create, append, move, rename, delete, listings, daily/random notes. Use when managing vault files.
Slim README.md (badges, quick start, docs index) with the detail moved into docs/ pages. Use when creating or auditing a README, splitting a long one, or adding badges.
Evaluate a skill by running test cases and grading results. Use when testing whether a skill produces correct guidance, validating improvements, or benchmarking before release.
Install, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
Merging release-please release PRs — batch merge, conflict resolution by closing and recreating the PR. Use when release PRs pile up or a release PR conflicts.
Execute a PRP with validation loop, TDD, and quality gates. Use when asked to execute a PRP, run a planned feature from docs/prps/, or delegate a PRP to subagents.
Version badge with build-info tooltip (version, commit, changelog). Use when adding version display to app header/footer for Next.js, Nuxt, SvelteKit, Vite, React, Vue, or Svelte.
Generate deployment handoff docs — tech stack, access URLs, config, monitoring, dev checklist. Use when handing off a service, documenting deployments, or creating client-facing summaries.