code-narrative-review

Analyze code readability and maintainability through narrative structure assessment.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/NlightNFotis/skills --skill code-narrative-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-narrative-review
Source: https://github.com/NlightNFotis/skills/tree/main/code-narrative-review
Command: npx skills add https://github.com/NlightNFotis/skills --skill code-narrative-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review code for readability, conceptual flow, naming quality, and maintainability when the logic works but the story of the code is hard to follow. It is designed for situations where reviewers or future maintainers struggle to build a clear mental model from a single pass.

Core Features & Use Cases

  • Narrative code review: Evaluates whether code introduces concepts in a sensible order, keeps a consistent point of view, and makes key decisions easy to find.
  • Naming and API clarity: Detects misleading names, broken promise-versus-delivery patterns, and abstractions that confuse callers.
  • Comment and structure audit: Separates useful explanatory comments from comments that merely compensate for unclear code, then prioritizes fixes such as renaming, reordering, extracting, inlining, or deleting.
  • Use Case: Use it when a large pull request passes tests but still feels difficult to review, or when a module keeps being misused because its names and flow do not match what readers expect.

Quick Start

Ask the AI to perform a code narrative review of a file, function, or pull request and identify the protagonist, confusing moments, naming issues, and highest-priority edits.

Frequently Asked Questions about code-narrative-review

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

FAQPage Schema
How do I review code for readability when the logic works but is hard to follow?

Code narrative review analyzes how clearly a module or function communicates intent, evaluating naming, flow, and comments to identify confusing moments and prioritize fixes like renaming, reordering, or extracting.

What is the best way to check API design and naming clarity for misleading abstractions?

Checking API design clarity involves detecting misleading names and broken promise-versus-delivery patterns, ensuring abstractions match what callers expect and preventing modules from being consistently misused.

How do I perform a structured assessment of a large pull request that passes tests but feels difficult to review?

Perform a structured assessment by identifying the code's protagonist and plot, locating narrative breaks, auditing comment quality, and generating prioritized recommendations such as inline, delete, or restructure.

When do I need a narrative code review instead of a standard functional check?

A narrative code review is needed during large refactors, API design checks, or onboarding-heavy modules when working code introduces concepts in confusing orders, making it difficult for maintainers to build a mental model.

How do I separate useful explanatory comments from comments that compensate for unclear code?

Separate explanatory comments through a comment and structure audit that evaluates whether comments clarify key decisions or merely mask bad abstraction levels, prioritizing fixes like renaming or restructuring.

Does code narrative review work for evaluating functions and individual files or only full pull requests?

Code narrative review works across modules, functions, individual files, and pull requests, applying structured assessments of naming, ordering, and abstraction levels to improve maintainability regardless of scope.