skills.rest
hashintel
hashintelOFFICIAL
Explore all skills by this author →
Website𝕏@hashaiGitHub

ln-review

Audit codebase architecture, module boundaries, and best practices.

7|Updated Mar 16, 2026
Search Tags:#architecture#code review#refactoring#software quality#module design
One-click install
npx skills add https://github.com/hashintel/brunch --skill ln-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ln-review
Source: https://github.com/hashintel/brunch/tree/main/.agents/skills/ln-review
Command: npx skills add https://github.com/hashintel/brunch --skill ln-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill assists software teams in auditing their codebase for quality, clarity, and architecture issues, helping improve maintainability and developer understanding.

Core Features & Use Cases

  • Code Architecture Assessment: Surface opportunities for modularization and structural improvements.
  • Best Practices Enforcement: Check for proper module boundaries, purity of functions, and unrepresentable invalid states.
  • Use Case: When refactoring a complex codebase, use this Skill to identify tightly coupled modules or side-effect drifts, guiding targeted refactors.

Quick Start

Ask the AI to review the codebase at the path 'src/' for architectural improvements.

Frequently Asked Questions about ln-review

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

FAQPage Schema
How do I review code architecture for module boundary violations?▼

Reviewing code architecture for module boundary violations involves analyzing module structures to identify tightly coupled components and side-effect drifts. This process surfaces opportunities for modularization and structural improvements to enhance maintainability and readability.

What is structural code review and how does it improve software quality?▼

Structural code review is an evaluation of code organization, naming, and function purity across modules to improve software quality. It ensures code adheres to design principles by identifying areas for architecture improvement and refactoring targets.

How do I audit my codebase to identify refactoring targets?▼

Auditing a codebase to identify refactoring targets requires evaluating module boundaries and checking for unrepresentable invalid states. This analysis highlights tightly coupled modules and side-effect drifts, guiding targeted refactors for better clarity.

Can I check my codebase for function purity and module design best practices?▼

Checking a codebase for function purity and module design best practices is possible by enforcing proper module boundaries. This ensures functions remain pure and invalid states are unrepresentable, directly supporting overall software quality.

When should I use architectural review instead of standard code review?▼

Architectural review should be used when refactoring a complex codebase to identify tightly coupled modules or side-effect drifts. Unlike standard code review, it focuses on structural design principles, module boundaries, and readability rather than line-level syntax.

Related Skills

Explore More Software Engineering Skills→
yu13130122297yu13130122297

scout

Identify uncertainties in research framing, datasets, metrics, and baselines.

Community
Intermediate
OrestesKOrestesK
2

improve-codebase-architecture

Identify refactoring opportunities that consolidate shallow modules into deeper ones.

Community
Advanced
knckknckknckknck

go-style-guide

Standardize Go code quality and style across projects.

Community
Intermediate
velesarvelesar
1

vp-s06-dependency-graph

Analyze and visualize software dependencies to detect coupling, cycles, and architectural violations.

Community
Advanced