code-quality
16.2K
write-script-rlang
MUST use when writing R scripts.
windmill-labs
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
16.1K
agent-native-reviewer
Reviews code to ensure agent-native parity -- any action a user can take, an agent can also take. Use after adding UI features, agent tools, or system prompts.
udecode
testing-security
code-quality
16.1K
architecture-strategist
Analyzes code changes from an architectural perspective for pattern compliance and design integrity. Use when reviewing PRs, adding services, or evaluating structural refactors.
udecode
testing-security
code-quality
16.1K
code-simplicity-reviewer
Final review pass to ensure code is as simple and minimal as possible. Use after implementation is complete to identify YAGNI violations and simplification opportunities.
udecode
testing-security
code-quality
16.1K
correctness-reviewer
Always-on code-review persona. Reviews code for logic errors, edge cases, state management bugs, error propagation failures, and intent-vs-implementation mismatches.
udecode
testing-security
code-quality
16.1K
maintainability-reviewer
Always-on code-review persona. Reviews code for premature abstraction, unnecessary indirection, dead code, coupling between unrelated modules, and naming that obscures intent.
udecode
testing-security
code-quality
16.1K
project-standards-reviewer
Always-on code-review persona. Audits changes against the project's own CLAUDE.md and AGENTS.md standards -- frontmatter rules, reference inclusion, naming conventions, cross-platform portability, and tool selection policies.
udecode
testing-security
code-quality
16.1K
resolve-pr-feedback
Resolve PR review feedback by evaluating validity and fixing issues in parallel. Use when addressing PR review comments, resolving review threads, or fixing code review feedback.
udecode
testing-security
code-quality
15.9K
flet-validation
Use when adding or changing validation for Python controls (dataclasses) in sdk/python/packages/, including Annotated/V rules, __validation_rules__, and property Raises docstrings.
flet-dev
testing-security
code-quality
15.8K
test-release
Verify a released archon binary works end-to-end via a specific install path. Use when: cutting a new release, reproducing a user bug report on the released version, or validating that a hotfix binary actually works after a re-tag. Triggers: "test the release", "test 0.3.1 via brew", "verify the curl install", "smoke test the binary", "did the release binary work", "run /test-release", "verify the release". NOT for: testing dev work (use bun link directly), testing unreleased changes (build locally via scripts/build-binaries.sh first), or running the full validate suite (bun run validate is separate).
coleam00
testing-security
code-quality
15.2K
be-code-style
Fix BE (C++) code formatting issues using clang-format
apache
testing-security
code-quality
15.2K
clang-tidy-check
Run clang-tidy on newly added/modified BE C++ code
apache
testing-security
code-quality
15.2K
fe-code-style
Fix FE (Java) code style issues using Checkstyle
apache
testing-security
code-quality
15.2K
batch-lint-cleanup
Analyze ESLint violations and auto-fix specific rules in isolation
ag-grid
testing-security
code-quality
14K
every-style-editor
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
EveryInc
testing-security
code-quality
14K
ce-update
Check if the compound-engineering plugin is up to date and fix stale cache if not. Use when the user says "update compound engineering", "check compound engineering version", "ce update", "is compound engineering up to date", "update ce plugin", or reports issues that might stem from a stale compound-engineering plugin version. This skill only works in Claude Code — it relies on the plugin harness cache layout.
EveryInc
testing-security
code-quality
14K
resolve-pr-feedback
Resolve PR review feedback by evaluating validity and fixing issues in parallel. Use when addressing PR review comments, resolving review threads, or fixing code review feedback.
EveryInc
testing-security
code-quality
14K
todo-resolve
Use when batch-resolving approved todos, especially after code review or triage sessions
EveryInc
testing-security
code-quality
14K
todo-triage
Use when reviewing pending todos for approval, prioritizing code review findings, or interactively categorizing work items
EveryInc
testing-security
code-quality
13.9K
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
mattpocock
testing-security
