skills.rest
benediktms
benediktmsCOMMUNITY
Explore all skills by this author →
Website𝕏@benediktmsGitHub

neocortex

Evaluate code changes for module boundaries, coupling, and abstraction fit.

Updated Mar 26, 2026
Search Tags:#architecture#dependencies#abstraction#coupling#code-review#modularization#system-design
One-click install
npx skills add https://github.com/benediktms/overmind --skill neocortex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: neocortex
Source: https://github.com/benediktms/overmind/tree/main/cli/claudecode-plugin/skills/neocortex
Command: npx skills add https://github.com/benediktms/overmind --skill neocortex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify architectural issues early by evaluating changes for system shape, module boundaries, coupling, and abstraction fit, helping teams avoid structural drift.

Core Features & Use Cases

  • Architectural review of changes for boundary respect, dependency direction, and symmetry with existing components.
  • Guidance for detecting problematic coupling, unclear abstractions, or risky integration points across modules.
  • Use Case: before merging a feature, run neocortex to surface architecture risks and required sign-off.

Quick Start

Provide a code change summary to neocortex and request an architecture review before merge.

Frequently Asked Questions about neocortex

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

FAQPage Schema
How do I perform an architecture review before merging code changes?▼

To perform an architecture review before merging, provide a code change summary to evaluate system shape, module boundaries, and abstraction fit. This surfaces structural drift, boundary violations, and required architectural sign-off prior to integration.

What is the best way to check module boundaries and coupling in a new feature?▼

Checking module boundaries and coupling involves evaluating dependency direction and integration risk. A structured review identifies problematic coupling, unclear abstractions, and symmetry issues with existing components across the codebase.

When do I need an architectural sign-off for new abstractions?▼

Architectural sign-off is needed when changes introduce new abstractions or touch existing module boundaries. Evaluating these changes for abstraction fit and system shape helps teams avoid structural drift and integration risks.

How do I detect problematic coupling and dependency direction across modules?▼

Detecting problematic coupling across modules requires a structured review of dependency direction and integration points. This process identifies unclear abstractions and evaluates whether new changes respect existing system boundaries and symmetry.

Can I assess system shape and integration risk for any codebase?▼

Assessing system shape and integration risk is applicable across codebases when changes touch boundaries or introduce new abstractions. The review evaluates structural drift, module boundaries, and coupling regardless of the specific platform.

Why does structural drift happen when introducing new abstractions?▼

Structural drift happens when new abstractions lack symmetry with existing components and violate module boundaries. Evaluating changes for system shape and abstraction fit early helps teams avoid this architectural degradation before merge.

Related Skills

Explore More Software Engineering Skills→
munluckymunlucky

backend-architecture

Provides knowledge graphs for backend architecture design focusing on layering and dependency management.

Community
Advanced
YanCheng-goYanCheng-go
3

commit

Automate branch creation, commits, PR review, and gated merge with human approval.

Community
Advanced
samjhechtsamjhecht
4

requesting-code-review

Dispatch a code-review subagent to verify implementation against plan or requirements.

Community
Basic
insightwavesmithinsightwavesmith

design-depth-check

Automate design depth analysis using evidence-shape-check.

Community
Basic