Skills for developer tooling and build systems: recovering and purging git history, repairing rebases, dependency conflicts and phantom dependencies, build cache misses and slow builds, affected-only monorepo builds, partial-release recovery and benchmark methodology.
Plugin devtools from marketplace greenblacked-ai in greenblacked/AI. Commands read from the repo's manifest — 2 days ago.
affected-build-selectionMakes a monorepo build and test only what a change can affect, without missing a regression. Affected means the change set against the merge-base mapped through the dependency graph in reverse; each step has a failure: a shallow checkout that degrades to everything or nothing, files outside the grap
benchmark-methodologyDesigns a trustworthy benchmark comparing two implementations, libraries or configurations, and gates CI on it without flaking. States the question and decision, controls the machine (pinned cores, fixed governor), warms up, runs separate processes, consumes results so the compiler cannot delete the
branch-rebase-repairRescues a branch whose rebase or merge produces dozens of bogus conflicts, usually because its base was squash-merged, cherry-picked or rewritten. Diagnoses first (the branch carries commits whose content already landed under other SHAs), finds the real boundary with merge-base --fork-point and the
build-cache-miss-huntExplains why a build or task cache keeps missing, then removes the volatile input. Measures hit rate per task type and the cold-then-warm ceiling on one commit, diffs the input hashes of a single task between two runs (turbo dry-run JSON, Gradle debug caching output, Bazel execution log), and checks
dependency-resolution-conflictUntangles an install that refuses to resolve, outside a planned major upgrade. Reads the whole conflict chain, names the two requirers that disagree and who owns each constraint (npm explain, pnpm why, pipdeptree --reverse, mvn dependency:tree -Dverbose, gradle dependencyInsight, go mod why -m), cla
git-history-purgeRemoves a committed secret, huge binary or private file from every ref, or shrinks a bloated repository. Rotates a credential first because a rewrite never un-leaks it, measures the real culprits with count-objects and a cat-file blob listing, rewrites a fresh mirror clone with git filter-repo (git
git-history-recoveryGets back commits, branches, stashes or a force-pushed tip that look gone. Freezes the repository first (gc.auto off, a copy of .git), then searches cheapest to costliest: reflog and ORIG_HEAD, fsck for dropped stashes and unreachable commits, the hosting push event or a teammate's remote-tracking r
partial-release-recoveryRecovers a release that stopped halfway, with some artefacts published and others not. Lists each step (registry, tag, GitHub release, image, docs) with its state and whether it can be undone, treats registries as append-only so a bad or half-finished version is rolled forward and the old one marked
phantom-dependency-auditFinds imports that work only through hoisting or an accidental transitive install, and declared dependencies nothing uses. Makes the environment strict rather than reading code: install without hoisting (pnpm's isolated layout) or resolve in a fresh virtualenv holding only the declared set, let fail
slow-build-profileProfiles a slow compile or bundle and attacks the biggest cost first. Takes three numbers before any change (clean build, incremental build after a one-line edit, no-op build), treats a no-op that does real work as a broken up-to-date check, then uses the toolchain's own profile (cargo build --timin
cache-key-diff-readerRead two build-cache key dumps for one named task, one from each machine (turbo dry-run JSON, Gradle build-cache debug output or a Bazel execution log), and return the single input that differs, classified as one of six culprit classes or as no input difference, so the whole-build dumps never enter
Skills for making games: build a playable prototype and take it to a finished game, hold a frame budget on the hardware you are shipping to, choose a multiplayer authority model and make it survive latency, tune numbers against telemetry instead of taste, and keep an asset pipeline from eating the build.
39 skills · 2 commands · 2 agents
Skills for the defensive side of shipping software: review a change for the vulnerability classes that actually get exploited, reduce who can do what toward least privilege without breaking production, rotate or contain a credential, harden a container image and keep checking it, read a Terraform plan for what it destroys, preserve evidence and build an intrusion timeline after a compromise, respond to credential stuffing, write and test detection rules, prove tenant isolation, handle vulnerability reports from outside researchers, and reverse engineer the binaries, managed CIL assemblies, APK packages, packaged apps, firmware and WebAssembly you are authorised to examine — including de-bloating a smart-TV or streaming device you own.
31 skills · 2 commands · 5 agents
Skills for the daily loop of changing code: review a diff for the defects that actually break production, debug a failure down to a proven cause, decide what to test before writing tests, restructure code without changing behaviour, orient yourself in an unfamiliar codebase, review a regex for catastrophic backtracking, write documentation that stays true, scaffold new production-ready code, design an API you can still evolve, land a dependency upgrade, build a website, and author a skill that fires when it should.
29 skills · 1 command · 5 agents
Skills for keeping a running system alive: triage a red pipeline to its real cause, get a broken Kubernetes workload back before diagnosing it, design alerts where every page is actionable, instrument a service so the next incident is answerable, write the runbook a stranger can follow at 3am, rehearse failure on purpose, plan for load before it arrives, and find out why the bill grew.
19 skills · 2 commands · 7 agents
Skills for engineering leadership: take over a team and audit what you inherited, record decisions, write status updates, run postmortems and incident comms, read delivery health, review on-call load, design the team cadence, a reorganisation and goals, make the case for headcount or for paying down tech debt, map team skills and single points of knowledge, plan onboarding, hire, benchmark pay, evaluate vendors, handle retention, growth reviews, improvement plans and difficult conversations, and assess how a team uses AI. Also ships two subagents, for reading contracts and synthesising feedback, and two commands.
22 skills · 2 commands · 2 agents
Skills for code that runs on a user's browser or phone: field performance, hydration, memory, version skew, service workers, CSP and Safari bugs, dates and locales, crashes, hangs, startup, battery, bad networks, on-device migrations, deep links, pushes and app size.
22 skills · 1 agent
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.
5 commands
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
Perform AI code review on Git diffs — supports workspace changes, branch ranges, and single commits with concurrent per-file analysis, codebase search, and deep context-aware review.
2 commands
Claude Code skill for creating and presenting Slidev slidedecks
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.