Skip to content

AgriciDaniel/claude-code-essentials-vs-code / templates/skills/code-quality

code-quality

Unverified

Enforce code quality standards

When writing or reviewing code:

  1. Follow project style guide (check CLAUDE.md first)
  2. Use meaningful variable names (no single letters except loops)
  3. Keep functions under 50 lines
  4. Add error handling for all external calls
  5. Write self-documenting code
  6. Avoid magic numbers (use named constants)
  7. Use early returns to reduce nesting
  8. Add JSDoc/docstrings for public APIs
  9. Prefer composition over inheritance
  10. Keep cyclomatic complexity low
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 318kUpdated Claude CodeCodexUnverifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 318kUpdated Claude CodeCodexUnverifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 318kUpdated Claude CodeCodexUnverifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 318kUpdated Claude CodeCodexUnverifiedInstall