AgriciDaniel/claude-code-essentials-vs-code / templates/skills/code-quality
code-quality
UnverifiedEnforce code quality standards
When writing or reviewing code:
- Follow project style guide (check CLAUDE.md first)
- Use meaningful variable names (no single letters except loops)
- Keep functions under 50 lines
- Add error handling for all external calls
- Write self-documenting code
- Avoid magic numbers (use named constants)
- Use early returns to reduce nesting
- Add JSDoc/docstrings for public APIs
- Prefer composition over inheritance
- Keep cyclomatic complexity low
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| 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 fallback | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| 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 always | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |