Product readiness auditor that crawls any codebase, maps what exists, identifies gaps, incomplete code, vulnerabilities, and dead ends, then produces a prioritized remediation plan. Trigger this skill when the user says 'inspect this project', 'audit my code', 'what's broken', 'product readiness check', 'MVP audit'…
Use when debugging, tracing, or mutating state in a running or testable Java application — inject code at method entry/exit, read/write fields, trace calls, throw exceptions, or verify behavior without recompiling.
Android Memory Leak Analyser & Solver — ingests LeakCanary traces from issue-tracker tickets, fetches tickets tagged as memory leaks from the configured issue-tracker board, or accepts raw traces pasted in chat. Identifies the reference chain, user journey, root cause, and reproduction steps. Generates a concise…
Diagnose why the current Claude Code session went wrong (or generally review how it went) using the Three Gaps framework (Understanding / Specification / Execution: Context / Tooling / Reasoning). MAIN spawns a fork to diagnose, presents findings, and applies any file fix only after explicit user approval — the fork…
This skill should be used when the user asks to "autofix pr", "fix pr locally", "fix ci failures", "fix review comments", "iterate on pr", "fix failing checks", "fix pr comments", "make ci green", "fix the build", "address reviewer feedback", or wants to iteratively fix CI failures and review comments on a GitHub PR…
Iteratively reviews recent code changes (a PR if one exists for the current branch, otherwise the branch's commit range) and fixes what the reviews find. Runs in-depth-review roles behind a workflow barrier each iteration (gh-style-review too, in iteration 1, when invoked with --gh-style), merges and deduplicates…
Debug a failed dynobox run from its terminal output. Use this skill when the user pastes or references output from npx dynobox run (especially --debug output with failed assertions), asks why a dyno run, scenario, or assertion failed, or wants a failing dyno fixed. Produces a root-cause diagnosis and proposed fixes…
Use when configuring Claude Code statusLine on Windows with PowerShell, especially when statusLine shows blank/empty or causes terminal layout corruption on exit.
Use this skill to investigate EC2 CPU exhaustion and performance degradation. Activate when: CPU utilization is high or at 100%, instance is slow or unresponsive, CloudWatch CPU alarm has triggered, T-series CPU credits are depleted, or the user reports performance issues on an EC2 instance. This skill provides…
Use when Codex Desktop on Windows cannot enable Computer Use, Any App works but Chrome is disconnected, or plugin caches/configuration for browser, chrome, and computer-use are missing or corrupted.
Plan, research, implement, debug, and verify software changes deliberately. Use for product or coding work that needs current technical choices, explicit tradeoffs, minimal-scope edits, and delivery-grade validation.
WeChat Mini Program automated build + debug workflow with version-based auto-selection between official Skills (wechatide CLI) and automator (miniprogram-automator). Covers npm build, appid verify, DevTools launch, 31 automation ops via helper daemon, and enriched E2E methodology requiring console/view/style checks at…
A workflow for solving China’s National Undergraduate Electronic Design Contest (TI Cup), from understanding a task to designing circuits, writing code, compiling, flashing, and debugging. It can generate wiring diagrams and support MCU, FPGA, simulation, and PCB work, but physical wiring, soldering, and instrument operation still need a person.
Deterministic simulation testing for containerized services. Write Lua scripts to inject chaos (pause, kill, resource deprivation) into Docker containers with reproducible, seeded fault injection. Use when writing chaos experiments, testing service resilience, or debugging distributed systems.
Trace the impact (blast radius) of a code change in ANY codebase and prove it didn't break anything else — language- and framework-agnostic. Use RIGHT AFTER a fix to a feature, function, module, type, route, API endpoint, schema, or config, before committing, opening a PR, or pushing. Triggers: "did this break…
Reduction-first coding for every change, whether building, fixing, refactoring, or cleaning up. Delete, merge, or replace before adding, so the project ends up smaller and simpler without losing anything the app needs, in code and in the text around it. Matters most for cleanups, refactors, and larger changes.
A template-repository issue-handling workflow for investigating reports from consumer repositories, reproducing problems, identifying root causes, and proposing fixes. After approval, it updates the shared template files and runs tests.
Automatically orchestrate multiple specialized agents working in parallel to debug, diagnose, and fix independent problems across different subsystems. Use when encountering 3+ unrelated bugs, test failures, or issues in isolated modules that don't share root causes. Match each problem to the right expert agent…
Top-down, whole-system audit of a codebase's DEEP LOGIC - the bugs that live in the SEAMS between modules, not inside any one file. Finds contracts that drift across module boundaries, invariants enforced on one path but broken on a sibling path, cross-cutting responsibilities (deletion cascade, tenant-scope…
Use when encountering any bug, test failure, or unexpected behavior — before proposing fixes.
★not rated 2 6mo agoA21 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: