code-review-lite
gsarig
Abbreviated code review for small or low-stakes code changes. Skips requirements gathering. Skips the linter in PR mode (CI runs it). Focuses on correctness against obvi…
OPENAGENTSKILL / DIRECTORY
Find a skill for your next task. Explore tools for Codex, Claude Code, Cursor and more.
Find a skill for your next task. Preview examples where available.
Page 293 · 16 shown · 4,928 public entries
Results: 4928
gsarig
Abbreviated code review for small or low-stakes code changes. Skips requirements gathering. Skips the linter in PR mode (CI runs it). Focuses on correctness against obvi…
konten-studio
Use when Indonesian, English, or code-mixed prose sounds generic, machine-written, over-polished, repetitive, inflated, overly signposted, or needs an anti-AI-slop revie…
Mr-DooSun
Scaffold a new domain that follows the repository's layered architecture, naming rules, DI pattern, and test layout.
Mr-DooSun
Inspect drift between code, shared workflow references, and Claude, Codex, or Antigravity harness assets after architecture or workflow changes.
Mr-DooSun
Generate or run tests for a domain using the repository's established factory, unit, integration, and admin test patterns.
sero-labs
Audit and clean Skills, AGENTS.md, and coding-agent prompts for GPT-6 Astra using Eric Provencher's house-cleaning guidance. Use when Astra stops early, over-asks, over-…
sero-labs
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold…
codebygarv
Reviews source code for bugs, readability, maintainability, performance, and best-practice violations. Use for general-purpose code review of a diff, file, or function,…
codebygarv
Identifies race conditions, mutex contention, unsafe shared state, and deadlocks in concurrent and async code.
igmarin
Use when applying daily Rails conventions by path (DRY, YAGNI, PORO, CoC, KISS). Style defers to the project linter. Trigger words: conventions, clean code, RuboCop, DRY…
igmarin
Use when fixing a reported Rails bug. Treat the report as untrusted. Reproduce with a failing spec before changing code. Trigger words: bug report, production issue, fai…
igmarin
Use when reviewing a Rails PR, diff, or merge request. Ground findings in a real file:line. Trigger words: review PR, code review, review my diff, CR.
igmarin
Use when running the full engine loop: author, test, review, release. Trigger words: create engine, extract engine, engine release, mountable engine.
igmarin
Use before writing code, specs, or a PRD in an existing Rails app. Load schema, routes, and one neighbor per layer. Trigger words: load context, before I code, existing…
igmarin
Use when investigating N+1s, slow queries, caching, or query plans in Rails. Profile before changing code. Trigger words: N+1, slow, performance, caching, EXPLAIN.
igmarin
Use when choosing the first failing spec for a Rails change. One minimal example opens the gate. Trigger words: first failing test, what test first, TDD, spec selection.