repo-sensemaker

Analyzes a repository and produces a Repository Sensemaking Brief. This skill is diagnostic, focusing on understanding the intent, structure, and fragility of a codebase to find the "weakest boundary."

Workflow

1. Analyze: Inspect README, core files, folder structure, and existing documentation.
2. Signal Detection: Identify what is working well (Strong Signals).
3. Gap Analysis: Identify what is absent or incomplete (Missing Pieces).
4. Evidence Gathering: Cite specific file paths and code snippets to back up signals and gaps.
5. Boundary Stress Test: Find the "Weakest Boundary" (e.g., mismatch between README and code, unsafe workflows, missing validation).
6. Synthesis: Produce a Repository Sensemaking Brief with candidate next steps and recommended workflows.

Output Format

Every response must follow the Repository Sensemaking Brief structure.

Boundary Rule

Do not execute workflows or implement changes. The output of this skill is a diagnostic artifact intended for consumption by workflow-orchestrator or a human.

References

• Repo Analysis Template
• Weakness Types
• Evidence Rules