act-code-reviewer
Review JusticeHub code against ACT ecosystem values. Enforces cultural protocols, ALMA principles, and regenerative design.
Find the perfect capability for your agent.
Review JusticeHub code against ACT ecosystem values. Enforces cultural protocols, ALMA principles, and regenerative design.
Use when cleaning up AI-generated code on a branch - identifies and removes unnecessary comments, defensive checks, type casts, and style inconsistencies that don't match the codebase
Systematic code review checklist for quality, correctness, and maintainability
Validates filenames against repository CLAUDE.md standards. Detects violations including uppercase letters, spaces, special characters, missing versioning, and incorrect patterns. Use when you need to check if files follow naming conventions before organizing or committing.
Perform comprehensive code reviews with focus on correctness, performance, security, and maintainability. Use when reviewing pull requests, merge requests, or code changes.
Write structured code review comments using Conventional Comments format.
This skill analyzes code for design quality improvements across 8 dimensions: Naming, Object Calisthenics, Coupling & Cohesion, Immutability, Domain Integrity, Type System, Simplicity, and Performance. Ensures rigorous, evidence-based analysis by: (1) Understanding code flow first via implementation-analysis protocol, (2) Systematically evaluating each dimension with specific criteria, (3) Providing actionable findings with file:line references. Triggers when users request: code analysis, design review, refactoring opportunities, code quality assessment, architecture evaluation.
This skill should be used when writing code, creating components, or implementing features. It provides the 23 essential coding standards that must be followed for every piece of code, ensuring scalable, efficient, and maintainable codebases.
Reviews code for unnecessary complexity and suggests simplifications that make it easier for developers to understand
Architecture analysis, violation detection, and pattern validation. USE WHEN: reviewing code architecture, identifying violations, verifying patterns, updating technical documentation. Reference: docs/02-architecture/ARCHITECTURE.md Examples: <example> Context: User wants to check if code follows architecture. user: "Analyze if the payment module follows our architecture" assistant: "I'll use architecture-analyzer to review against ARCHITECTURE.md." <commentary>Architectural review is architecture-analyzer specialty.</commentary> </example> <example> Context: Need to identify technical debt. user: "Find architectural violations in the services layer" assistant: "I'll use architecture-analyzer to scan for violations." <commentary>Violation detection is architecture-analyzer responsibility.</commentary> </example>
inkLine code quality and simplification guidelines ensuring clear, consistent, maintainable code
Defines project-wide code conventions for magic number elimination, constant usage, performance optimization, and coordinate system separation. Use when implementing, testing, or reviewing code to ensure consistency across the codebase.
Guide for writing clean, maintainable, professional code. Covers meaningful naming, function design, formatting, error handling, comments, and code smells.
Write self-documenting code with clear structure and naming, using minimal but helpful comments only when necessary to explain complex logic. Use this skill across all code files when deciding whether to add comments or how to structure code for clarity. Use when refactoring code to be more self-explanatory, when removing outdated or temporary comments, when writing evergreen informational comments that remain relevant over time, or when choosing between adding a comment versus improving variable/function names. Apply when working with any programming language (.ts, .js, .py, .java, .go, .tsx, .jsx, .vue) to maintain clean, understandable code without over-commenting.
Comprehensive C# code validation, static analysis, and best practices verification for .NET applications. Use when validating C# code, checking SOLID principles, reviewing async/await patterns, verifying nullable reference types usage, checking Entity Framework queries, ensuring security best practices, or reviewing .NET code quality and architecture.
Review functional area and component documentation to check that it adheres to repo standards.
Performs thorough code review with focus on correctness, security, performance, and maintainability. Provides actionable feedback with specific line references.
Identify and remove unused code, commented blocks, unreachable code, and unused imports. This skill should be used during Phase 1 cleanup tasks to improve codebase maintainability.