Total 30,734 skills, Code Quality has 1622 skills
Showing 12 of 1622 skills
Structures the human review experience for factory-mode builds. Audit trail summaries, PR digests, retrospective synthesis, quality trend tracking, and autonomy tuning interface. Activate during Phase 3 human review.
Three-stage code review protocol: spec compliance, code quality, and domain integrity. Activate when reviewing code, preparing PRs, assessing implementation quality, or checking that code matches requirements. Triggers on: "review this code", "prepare PR", "check implementation", "code quality", "does this match the spec".
Domain modeling principles: parse-don't-validate, make invalid states unrepresentable, primitive obsession detection, semantic types, and domain veto authority. Activate when designing types, reviewing code for domain integrity, or when domain review is needed in a TDD cycle.
Systematic 4-phase debugging: understand the failure, form hypotheses, test one change at a time, fix with confidence. Activate when tests fail unexpectedly, errors occur, behavior is wrong, or something that worked before is now broken. Triggers on: "debug", "why is this failing", "test failure", "unexpected error", "bug", "broken".
Professional Code Auditor for Angular Enterprise Architecture. Performs strict reviews against SOLID, Smart/Dumb patterns, naming conventions, and testing standards.
Deep thinking mode - approach problems like a craftsman, obsess over details, and create elegant solutions
TypeScript strict patterns and best practices. Trigger: When writing TypeScript code - types, interfaces, generics.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Implement features and write code based on tasks in Plans.md. Use this when the user mentions implementation, adding features, writing code, or creating new functions. Do not use for review or build verification.
Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", or "technical debt". Covers smell-driven refactoring, safe transformation sequences, and testing guards. For code quality foundations, see clean-code. For managing complexity, see software-design-philosophy.
Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions "best practices", "pragmatic approach", "broken windows", "tracer bullet", or "software craftsmanship". Covers estimation, domain languages, and reversibility. For code-level quality, see clean-code. For refactoring techniques, see refactoring-patterns.
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", or "use case boundary". Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.