Claude Skills by ravidsrk

Drain a maintainer's inbound pull-request queue: every open contribution is absorbed with the contributor's authorship preserved and a RED-on-base / GREEN-on-head regression receipt, refuted with a reproduction attempt on current main, closed as superseded or duplicate citing the winning SHA, or parked with a named ask to the contributor. The unit is one inbound PR — someone else's diff, not your finding. Use when "review and merge the open PRs", "drain the PR queue", "absorb these community ...

Drive a FROZEN page/flow/component set to WCAG 2.2 AA conformance (the engineering target that satisfies EAA / ADA / Section 508, which formally reference WCAG 2.1/2.0): a deterministic axe-core oracle clean on the surface plus a mandatory negative control (revert the fix, the violation returns), with the hard ~30-40% automation ceiling forcing screen-reader and cognitive criteria into a first-class human-AT park. The unit is one success-criterion violation instance on the frozen surface. Use...

Prove a codebase or change-set conforms to a standard — EU AI Act Art-12/50, SOC 2, NIST SSDF — with auditor-grade, independently re-derived evidence, or name the gaps. The unit is one obligation from a FROZEN standard catalog (standard@version), not a discovered finding: enumerate the obligations, gather evidence bound to authoritative state for each, have an independent session re-derive it, and mark each control VERIFIED or GAP. Use when "prove compliance", "conformance", "audit-ready evid...

Exhaust a finite backlog of findings to zero, PR-per-finding, on Orca. Sources: an audit/adversarial-review document, the issue tracker, or verified false documentation claims. Each finding is skeptic-triaged (reproduced or refuted with evidence), fixed on an integration branch with a failing-first test, build-blind reviewed, merge-verified, and closed with a linked SHA; the loop re-enumerates until dry. Use when the backlog is yours to merge: "clean sweep", "close every open issue", "drain t...

Eliminate intermittent test failures to a declared confidence contract. Detect flakes by repeat- run + CI retry history, diagnose each with a loop that RAISES the failure rate (never a theory), fix the root cause and ratchet it red-by-revert, then re-run the whole suite for a consecutive green streak — local AND in CI — looping until the streak holds. Retry-wrappers as fixes are banned and grep-checked. Use when "kill the flaky tests", "deflake the CI", "flake zero", a flaky/intermittent suit...

Cover a public surface with documentation that is true: extract the surface with a script at the base head, map coverage per Diataxis quadrant by grep-able evidence, freeze the gap list, write one cell per unit reference-first from code archaeology, and bind every factual claim to a file:symbol or a pasted run — with the negative control that renaming the anchored fact turns the claim check RED. The unit is one (public-surface entity x quadrant) cell. Use when "document this project", "our do...

Verify an app on a real device or emulator and fix what only hardware shows: pair a device session through Orca's emulator/device skills, capture a pre-change regression baseline, reproduce the defect on-device with captured artifacts, fix it, and re-verify the same flow on- device at the head SHA — with the negative control that reverting the fix reintroduces the on- device failure. The unit is one device-observed defect (or one device QA pass over a flow). Use when "test on a real device", ...

Install a written, numbered, tool-enforced quality bar for a repo: detect the constraint dimensions (coverage, security scanning, perf budgets, a11y, architecture boundaries) with measured current values, freeze them with thresholds into a committed CONSTRAINTS.md at a human gate, wire one machine check per dimension, and prove every gate FIRES — on an injected violation in a throwaway worktree before CI, and on a canary PR that must fail CI after — then guard the bar itself against quiet low...

Establish a threat model and close it: audit → prove exploits → fix → RE-ATTACK the fix and audit the whole vulnerability class → re-audit, looping until a fresh full audit finds zero unrefuted P0/P1. STRIDE + OWASP Top 10 + OWASP LLM Top 10 + supply-chain. Use when the ask is the whole adversarial loop: "harden this", "red team", "close the security loop", "harden this service against SQL injection and auth bypass", "audit then exploit then re-attack", or an unattended audit-fix-verify run. ...

Resolve a foggy, multi-session goal into a frozen execution map that ship-it can consume — decisions, not deliverables. Chart a fog-of-war map of decision-tickets (only ticket what you can phrase sharply now), clear the research/decision frontier in parallel with HITL at each decision, and produce a frozen plan + a prepared DAG. Use when the goal is too big/foggy for one session, "chart this", "plan this epic", "I don't know the shape yet", or you can't yet authorize implementation. Its outco...

Land a stateful schema or data change across deploys with old and new code valid at every step: expand → dual-write → backfill → switch reads → zero-readers → retire-writes → zero-writers → contract, each phase its own deployed and baked change, each with a down path that was written AND run, dual-validity proven both directions, and a parity probe GREEN after backfill and archived before the old shape is dropped. The unit is one migration PHASE of one table or shape. Use when "migrate the da...

Bring a dependency / framework / platform surface current, safely — CI green at every merge. Inventory outdated + advisories with reachability triage → order by a compatibility graph → upgrade one dep or coherent group per PR, adapting call sites (code-level expand/migrate/contract) to get off old majors while keeping CI green → re-inventory until every major is current or pinned-with-a-reason. Use when "update the dependencies", "upgrade everything", "framework migration", "get off the old m...

Make a surface operable: every path in a frozen set answers its on-call questions from telemetry alone, every alert is symptom-based with two severities and a justified threshold, every alert has a linked runbook and has been test-fired, and an induced staging failure is located by a fresh worker with NO source access — the oracle a narrator cannot fake. The unit is one path times its 2-4 on-call questions. Use when "make this operable", "we were blind during the incident", "add observability...

Turn a bounded set of issues on a repo you do NOT control into landed open-source contributions. Each actionable issue is skeptic-triaged (including a search of the upstream repo's OPEN PRs, not just its code), built on a fork with a failing-first test, reviewed build-blind, and opened as an etiquette-correct PR against the upstream default branch — or, where a maintainer PR already exists, shared as a quoted review- assist comment (an alternative PR only if maintainers invite one). The loop ...

Re-witness and re-pin the fleet's runtime-mechanics doctrine against the installed control-plane binary after an upgrade or a drift signal: enumerate every mechanics claim in runtime policies, scripts, and mission dispatch preambles, load the version-matched guides the binary serves, replay each claim live, and patch what lags — kept claims carry receipts, removed claims carry archived refutations. The unit is one mechanics claim. Use when "Orca updated", "re-pin the runtime contract", "polic...

Give every critical path a test that dies under a behavior-changing mutation. Map the untested critical surface (coverage × call-graph of the money/auth/data paths), write characterization tests that assert real behavior, prove each earns its keep by failing at its assertion under a mutation (harness still runnable — a compile break is not proof), and route surfaced bugs to a fix or backlog, looping until every confirmed critical path is mutation-audited. Use when "close the test gap", "cover...

Deepen a lived-in codebase's confirmed hot modules without changing behaviour: a churn-weighted shallowness inventory finds the modules whose interfaces are too wide for what they hide, a human confirms the target surface, a mutation-audited characterization net (prove-it's, consumed here) is pinned BEFORE any restructure, and each module is deepened one seam at a time with build-blind review. The unit is one module-deepening (one interface shrink at one seam). Use when "this module is a god ...

Produce a trusted, read-only, SHA-bound verdict on a PR or branch — no fixing authority. Acceptance review (standards, frozen-spec compliance, test-adequacy) always; scope-triggered risk lenses (security, performance, accessibility, data-migration) when the change surface warrants. Findings quote their motivating line, carry severity, and are bound to the reviewed SHA. Use when "review this PR", "review this diff", "is this diff ready to merge", "review this PR for accessibility", "check this...

Find the demonstrated root cause of a hard bug that has neither a frozen spec nor an enumerable backlog — a flaky failure, an intermittent production symptom, a concurrency bug, an unexplained regression. Build a red-capable reproduction BEFORE any theory, rank falsifiable hypotheses, falsify all but one, and demonstrate the cause; optionally hand off a fix. Use when "diagnose this", "why is this happening", "why does this fail only in CI", "find the root cause", "debug this hard bug", diagno...

Turn intent or a frozen spec into a released, verified outcome on Orca. Entry is either a frozen spec (validate → decompose) or raw intent (grill → freeze → decompose); after freeze both enter one canonical pipeline: decompose → build (tested slices) → acceptance review → runtime-prove → land → release → observe, stopping at the highest release state you're authorized to reach (BUILT / PROMOTION_READY / RELEASED / DEPLOYED_AND_VERIFIED). Use when "build and ship this", "spec to shipped produc...

Bring declared user journeys within pre-declared performance budgets, proven by measurement. Controlled baseline (measure to a metric contract, not once) → profile the real bottleneck → fix PR-per-hotspot with a mandatory before/after → re-benchmark to the metric's statistical contract → add CI regression guards, looping until every journey is within budget or parked. Use when "the app is slow", "perf sweep", "Core Web Vitals", "LCP regression on mobile", "get under budget", or an unattended ...