Total 30,741 skills, Code Quality has 1622 skills
Showing 12 of 1622 skills
Guiding principles for writing clear, concise, human readable and maintainable Python code.
Structured code review covering style, readability, and security concerns with actionable feedback. Use when reviewing pull requests or merge requests to identify issues and suggest improvements.
Apply SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion) for systematic development. Use for feature development, TDD workflows, and structured problem-solving.
Software engineering best practices for code review. Use when reviewing code, analyzing code quality, checking for bugs, security vulnerabilities, or providing feedback on code changes.
Applies software engineering best practices, design principles, and avoids common anti-patterns. Use when designing systems, reviewing code quality, refactoring legacy code, making architectural decisions, or improving maintainability.
Use when prettier integration with editors, pre-commit hooks, ESLint, and CI/CD pipelines.
Pre/post-operation validation to detect missing components and prevent future issues
Run full validation to ensure code is ready for merge. Use before merging PRs, when asked to validate readiness, or as a final check before requesting review.
Remove AI-style noise from staged and branch diffs while preserving behavior and repository style.
Run Codex CLI /review via tmux to review uncommitted changes. Launches Codex in isolated tmux session, sends /review command, selects option 2, captures output. Use when you want a second opinion on uncommitted code changes.
Code quality standards — lint (eslint/oxlint), type check (tsc), pre-commit hooks, and comment conventions. All comments must be in English.
Check code quality and formatting before committing changes