Loading...
Loading...
Found 102 Skills
Audit a codebase for adherence to the Spectrum design system and React Spectrum S2 best practices. Use when a developer asks to audit, review, lint, or check a project for Spectrum/S2 correctness, configuration, styling, accessibility, or component-usage issues.
Review existing Rust code for idiom, API design, error handling, safety, and maintainability, and produce a prioritized report where every finding cites the rule it breaks and gives a concrete fix. Use this whenever the user asks to review, audit, critique, grade, or "check" Rust code, a crate, a module, a .rs file, a diff, or a pull request, or asks what is wrong with their Rust or how to make it more idiomatic, even if they don't say "review". Pairs with the rust-best-practices skill, which covers writing new code.
Filament rules review. Use when the user asks to check Filament code against the project's Filament ways, or when another skill needs a Filament review of the code it touched.
Deep audit of a Frappe app for security, correctness, and customization defects. Runs every security scope and every quality rule in a separate agent, verifies each candidate in a fresh context, and compiles one report. User-invoked only - run /deep-app-audit [app path] [options].
End-to-end defect hunt and repair across a whole codebase - context and business-rule capture, hierarchical sweeps (business logic, error handling, security, correctness, concurrency, data integrity, performance, config, test quality), reproduction, root-cause fixes, regression proofing, and an evidence-backed audit report. Use whenever bugs are to be found or fixed at repository or module scope, such as "find all the bugs", "fix everything", "audit this codebase", "review the whole codebase", "QA review", "harden this before release", "check for vulnerabilities", "why is this flaky". Use it equally for business-logic defects where nothing crashes but the result is wrong - "the calculation is wrong", "the numbers do not add up", "the discount applies twice", "a step can be skipped", "the request can be replayed", "the limit does not hold", "a user can see another user's data". Prefer this over ad-hoc reading whenever the scope is a repo, a module, or "everything" rather than one known failing line, and when reviewing AI-generated or recently merged code before shipping. This skill CHANGES CODE. If the user wants findings only with nothing modified - "review only", "do not touch anything", "report only" - use anti-bug-review instead.
Planning a whole-codebase simplification: audits a Go/TS codebase for needless abstraction and emits a KILL/REVIEW/KEEP plan plus a ring:running-dev-cycle task array. Plans only — no edits. Detects single-impl interfaces, pass-through shims, translation-free adapters, and dead-code cascade chains under an inverted burden of proof. Use for pre-public or post-pivot cleanup. Skip for current diff review (use ring:reviewing-code).