Agent skill · Code Review & Quality

code-quality

Agents should invoke this skill for code reviews, linting/formatting setup, maintainability checks, complexity concerns, warning cleanup, coding standards, or quality gates in Rust, TypeScript, Python, shell, and mixed repos.

Wayner Barrios443★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add waybarrios/opencode-power-pack --skill code-quality --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: skills/code-quality/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 443
Language: JavaScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Code Quality Structured code review and quality enforcement across common tech stacks. Checklists, linting strategies, and metrics to keep codebases healthy. ## Quick Start ### Run a Code Quality Check 1. **Run static analysis:** Linters, type checkers, formatters 2. **Review against checklist:** Language-specific items below 3. **Check complexity metrics:** Cyclomatic < 25, data flow < 25 4. **Report findings:** Structured output with severity and recommendations --- ## Linting Configurations ### Rust — Clippy Config Standard clippy configuration (in `Cargo.toml` or `.clippy.toml`): ```toml [lints.clippy] cognitive_complexity = "warn" pedantic = { level = "deny", priority = -1 } nursery = { level = "deny", priority = -1 } unwrap_used = "deny" ``` **Standard commands:** ```bash cargo fmt cargo clippy --all-targets --all-features -- -D warnings cargo check cargo test -- --test-threads=1 ``` **Key rules to enforce:** - No `.unwrap()` in non-test code (use `?` or `.expect("reason")`) - All public items have rustdoc (`#[warn(missing_docs)]`) - `#[must_use]` on functions that return values that should be checked - When using `#[allow(...)]`, always add a comment explaining why - If no

What's inside
Steps it walks through
  1. Quick Start
  2. Run a Code Quality Check
  3. Linting Configurations
  4. Rust — Clippy Config
  5. TypeScript — ESLint + Strict Mode
  6. Python — Ruff + Mypy
  7. Code Review Checklists
  8. Universal Checklist (All Languages)
  9. Rust-Specific Checklist
  10. TypeScript/React-Specific Checklist
  11. Django/Python-Specific Checklist
  12. Complexity Metrics
  13. Cyclomatic Complexity
  14. Data Flow Complexity
Commands it runs
cargo fmt
cargo clippy --all-targets --all-features -- -D warnings
cargo check
cargo test -- --test-threads=1
More from opencode-power-pack
All skills →
About this skill
What does the code-quality skill do?

Agents should invoke this skill for code reviews, linting/formatting setup, maintainability checks, complexity concerns, warning cleanup, coding standards, or quality gates in Rust, TypeScript, Python, shell, and mixed repos.

How do I install it?

Run `npx skills add waybarrios/opencode-power-pack --skill code-quality --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From waybarrios/opencode-power-pack, a repository with 443 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going