power-mapper

Audit entire repositories to document files, features, integrations, and gaps.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/richyparr/power-mapper --skill power-mapper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: power-mapper
Source: https://github.com/richyparr/power-mapper/tree/main
Command: npx skills add https://github.com/richyparr/power-mapper --skill power-mapper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Large AI audits miss files, features, and integrations because LLMs cannot reliably enumerate a repository, leaving security, product, and compliance questions open; power-mapper uses bash scripts and orchestrated agents to guarantee that every file is analyzed, every endpoint is traced, and every gap is documented before any executive report is issued.

Core Features & Use Cases

  • Hierarchical MapReduce architecture: Tier 1 bash scripts capture every file, Tier 2 Sonnet agents analyze chunks, Tier 3 synthesizes domains, Tier 4 traces cross-cutting concerns, Tier 5 Opus generates FEATURES, GAPS, and AUDIT-SUMMARY, and Tier 6 verifies 100% coverage.
  • Derivatives for downstream tooling: CODEBASE-CONTEXT.md energizes future AI sessions, DEPENDENCIES.md maps impact, SECURITY-BASELINE.md surfaces auth/API risks, TEST-MAP.md informs E2E planning, and CLEANUP.md lists dead-code targets.
  • Use case: Run a full audit before onboarding a new team, planning a refactor, or delivering a security review so you have a deterministic feature inventory, integration audit, and technical debt report ready in minutes.

Quick Start

Ask power-mapper to run a full audit of this repository so every file, feature, and endpoint is mapped and verified.

Frequently Asked Questions about power-mapper

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

FAQPage Schema
How do I audit a large codebase to ensure every file and endpoint is documented?

A codebase audit works by applying tiered bash enumeration and orchestrated Sonnet and Opus agents to trace cross-cutting concerns and verify 100% coverage before generating an executive report.

How do I generate a complete feature inventory for an enterprise repository?

Generating a complete feature inventory requires running orchestrated agents across repository chunks to synthesize domains and output deterministic feature lists, integration maps, and technical debt reports.

Can I use bash enumeration to verify 100% coverage on repositories with 1M+ lines of code?

Yes, bash enumeration supports enterprise codebases from 10K to 1M+ LOC by capturing every file in tier 1, allowing downstream agents to analyze chunks and trace cross-cutting concerns.

What is the best way to map integration endpoints and security risks before a refactor?

Mapping integration endpoints and security risks involves running a full audit to surface auth/API risks in a SECURITY-BASELINE.md and map dependencies in a DEPENDENCIES.md file for downstream tooling.

Why do large AI codebase audits miss files and integrations?

Large AI audits miss files because LLMs cannot reliably enumerate a repository, leaving gaps; using bash scripts and verification scripts ensures every file is analyzed and every gap is documented.