paw-code-research

Document codebase component interactions with exact file:line references.

39|6|Updated Oct 8, 2025
One-click install
npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-code-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paw-code-research
Source: https://github.com/lossyrob/phased-agent-workflow/tree/main/skills/paw-code-research
Command: npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-code-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill documents exact locations of code components with file:line references to create a durable map of the codebase for planning, auditing, and onboarding.

Core Features & Use Cases

  • Document implementation details with file:line references
  • Discover documentation infrastructure (framework, config, conventions)
  • Trace data flows and component interactions
  • Find code patterns and integration points
  • Generate GitHub permalinks when on pushed commits
  • Conduct additional research on demand

Quick Start

Run the paw-code-research skill to map full codebase and generate a CodeResearch.md artifact with file:line evidence.

Frequently Asked Questions about paw-code-research

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

FAQPage Schema
How do I document codebase architecture with precise file:line references for traceability?

Documenting codebase architecture with file:line references involves mapping exact component locations and interactions into a durable CodeResearch.md artifact, providing traceability evidence for planning, auditing, and onboarding.

How do I map data flows and component interactions across a complex software project?

To map data flows and component interactions, run an automated analysis that traces integration points and patterns across the codebase, outputting detailed notes with specific file:line evidence to a central markdown document.

Can I generate GitHub permalinks for code documentation when refactoring on pushed commits?

Yes, generating GitHub permalinks for code documentation is supported when operating on pushed commits, ensuring that file:line references in the research artifact remain durable and directly accessible during refactoring phases.

What's the best way to discover documentation infrastructure and conventions in an unfamiliar codebase?

The best way to discover documentation infrastructure is to conduct codebase research that identifies the framework, configuration, and conventions, compiling these findings with verification commands into a structured markdown report.

Do I need a specific environment setup to document file:line evidence for codebase auditing?

No specific dependencies or environment components are required to document file:line evidence for codebase auditing, making it straightforward to generate traceability maps and verification commands in any standard software project.