aip-code-correlator

Correlate AIP review findings to code locations in NestJS, Fastify, and Express projects.

Updated Dec 10, 2025
One-click install
npx skills add https://github.com/getlarge/claude-aip-plugins --skill aip-code-correlator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aip-code-correlator
Source: https://github.com/getlarge/claude-aip-plugins/tree/main/plugins/aip-api-design/skills/aip-code-correlator
Command: npx skills add https://github.com/getlarge/claude-aip-plugins --skill aip-code-correlator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Correlate AIP review findings with concrete code locations in code-first API projects, enabling faster fixes, better traceability, and easier work planning.

Core Features & Use Cases

  • Preferred MCP approach: Use mcp__aip-reviewer__aip-correlate when available to automatically map findings to code locations across NestJS, Fastify, and Express projects.
  • Manual fallback: If MCP tools are unavailable, manually derive file/line references from findings and operation context to guide fixes.
  • Outputs: ExtendedFinding[] with file:line references; suggested diffs for deterministic fixes; save correlations to thoughts/api/correlations.

Quick Start

Provide reviewId and projectRoot to start correlation; optionally specify specPath for context; framework hints help speed up the location search.

Frequently Asked Questions about aip-code-correlator

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

FAQPage Schema
How do I map API findings to code locations in my NestJS or Express project?

Code correlation automatically maps AIP review findings to specific file and line references in NestJS, Fastify, and Express codebases. It extracts operations from findings, locates corresponding endpoint implementations, and outputs ExtendedFinding structures with precise code locations to accelerate fixes and improve traceability.

Can I correlate OpenAPI spec paths to source files in a code-first API project?

Yes. The Skill correlates OpenAPI-derived findings to concrete code locations by detecting your framework from package.json, extracting operations from findings, and identifying endpoint implementations. It supports both MCP-based automatic correlation and manual fallback workflows for Express, NestJS, and Fastify projects.

What happens if MCP tools aren't available for AIP correlation?

A manual fallback workflow derives file and line references directly from findings and operation context to guide fixes. You provide reviewId and projectRoot; the Skill generates ExtendedFinding structures and suggested diffs even without MCP integration, saving correlations to thoughts/api/correlations.

Does code correlation work with Fastify and Express, or just NestJS?

Code correlation supports NestJS, Fastify, and Express. The Skill detects your framework automatically from package.json, then maps findings to corresponding code locations across all three frameworks with equal precision and output consistency.

What output do I get after correlating AIP findings to code?

Correlation outputs ExtendedFinding arrays with file:line references pinpointing where fixes apply, suggested diffs for deterministic code changes, and saved correlations stored in thoughts/api/correlations for audit and work planning.