Skip to content
Back to skills

Code Quality

ASecurity

| Principle | Description | |-----------|-------------| | SRP | One responsibility per function/class | | DRY | Don't Repeat Yourself | | KISS | Keep It Simple | | YAGNI | You Aren't Gonna Need It | | naming | Clear, descriptive names | - [ ] Code compiles without errors - [ ] Tests pass - [ ] No console.log/debug code - [ ] Types are correct - [ ] No hardcoded secrets - [ ] Logic is correct - [ ] Error handling is proper - [ ] Performance is acceptable - [ ] Security

  • 14 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 7, 2026
code-qualitygotestingsecurityperformance

Security analysis

A100/100

Scanned September 7, 2026

npx -y skills add modbender/skill-library-mcp --skill code-quality --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Quality?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Quality
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/modbender-code-quality/badge)](https://www.skillsdirectory.com/skills/modbender-code-quality)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
# Code Quality & Reviews

## Clean Code Principles

| Principle | Description |
|-----------|-------------|
| SRP | One responsibility per function/class |
| DRY | Don't Repeat Yourself |
| KISS | Keep It Simple |
| YAGNI | You Aren't Gonna Need It |
| naming | Clear, descriptive names |

## Code Review Checklist

### Before Submitting
- [ ] Code compiles without errors
- [ ] Tests pass
- [ ] No console.log/debug code
- [ ] Types are correct
- [ ] No hardcoded secrets

### Review Points
- [ ] Logic is correct
- [ ] Error handling is proper
- [ ] Performance is acceptable
- [ ] Security considerations
- [ ] Code is readable

## PR Standards

```markdown
## Description
Brief description of changes

## Type
- [ ] Bug fix
- [ ] Feature
- [ ] Refactor

## Testing
- [ ] Unit tests added
- [ ] Integration tests pass

## Screenshots (if UI)
```

## Checklist

- [ ] Follow naming conventions
- [ ] Write self-documenting code
- [ ] Keep functions small
- [ ] Handle errors properly
- [ ] Add comments for complex logic
- [ ] Review your own PR first

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…