code_review

Analyze Go repositories for architectural flaws and generate prioritized remediation plans.

4|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/dewitt/swarm --skill code-review-dewitt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code_review
Source: https://github.com/dewitt/swarm/tree/main/skills/code_review
Command: npx skills add https://github.com/dewitt/swarm --skill code-review-dewitt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to systematically identify architectural flaws, dead code, and maintenance bottlenecks in large codebases, providing actionable recommendations to improve reliability and readability.

Core Features & Use Cases

  • Static & structural analysis: audits architecture, coupling, and idiomatic patterns.
  • Documentation alignment: checks README.md and inline comments against implementation.
  • Risk-focused reporting: surfaces critical issues, suggested fixes, and implementation plans.

Quick Start

Review the current repository state and surface top-priority improvements for immediate action.

Frequently Asked Questions about code_review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find architectural flaws and robustness gaps in a Golang codebase?

To find architectural flaws in a Golang codebase, you need a comprehensive code review that applies static analysis tools like go vet and golangci-lint to identify coupling issues, dead code, and maintainability bottlenecks. This process audits structural patterns and generates a prioritized remediation plan to improve reliability and readability.

What is the best way to check if README documentation aligns with Go implementation?

The best way to check documentation alignment is to perform a documentation review that audits inline comments and README.md files against the actual Go implementation. This ensures your documentation accurately reflects the codebase, preventing maintenance bottlenecks and improving overall readability.

How do I generate a prioritized remediation plan for scalability issues in Go?

To generate a prioritized remediation plan for scalability issues in Go, run a risk-focused code review that combines static analysis, unit tests, and structural audits. This surfaces critical maintainability issues and provides actionable recommendations for immediate implementation.

Does golangci-lint support detecting dead code and maintenance bottlenecks in large repositories?

Yes, golangci-lint supports detecting dead code and maintenance bottlenecks by running static analysis on your Go repository. When integrated into a structural code review, it identifies idiomatic pattern violations and architectural flaws, providing a comprehensive view of your codebase's health.

Can I use static analysis to assess dependencies and unit test coverage for Go projects?

Yes, you can use static analysis to assess dependencies and unit test coverage in Go projects. A comprehensive code review evaluates your test suite alongside architectural coupling, ensuring your codebase meets robustness and scalability requirements while identifying critical gaps.

Why does my Go codebase need a structural code review before scaling?

Your Go codebase needs a structural code review before scaling to systematically identify architectural flaws and dead code that create maintenance bottlenecks. This review provides actionable recommendations to improve reliability and readability, ensuring your codebase can handle increased scalability demands.