Analyze codebase questions by reading multiple files and citing concrete references.
npx skills add https://github.com/RJJJJ/project2 --skill analyze-rjjjj
Please help me install this Agent Skill. Skill: analyze Source: https://github.com/RJJJJ/project2/tree/main/.codex/skills/analyze Command: npx skills add https://github.com/RJJJJ/project2 --skill analyze-rjjjj
Read-only, evidence-based explanations of complex codebase questions, eliminating guesswork and avoiding edits while exposing sources and confidence levels.
Ask to analyze the repository in read-only mode and return a grounded, ranked synthesis with evidence and sources.
High-intent search queries and answers about installing and using this skill.
To get an evidence-based codebase analysis without modifying files, request a read-only repository review. The system reads multiple files across modules to synthesize explanations and cites concrete file paths and lines while keeping edits out of scope.
The best way to find concrete file references for complex code questions is to use a ranked synthesis approach. It evaluates multiple files across modules and presents a grounded explanation that explicitly cites the exact file paths and lines supporting each conclusion.
Yes, you can separate proven evidence from inferred logic when analyzing a repository. The analysis emphasizes an explicit evidence-vs-inference boundary, ranking explanations and exposing provenance and confidence levels to distinguish verified facts from inferred conclusions.
To analyze a read-only repository across multiple modules, apply the analysis to the repository context and request a grounded synthesis. It reads across modules, ranks explanations, and provides a non-destructive review with explicit sources.
No, this code analysis approach does not propose code edits or refactoring changes. It is a non-destructive tool designed to provide evidence-based explanations and confidence levels, keeping all modifications and edits explicitly out of scope.
spencerbeggsAnalyze repository file structures to determine project type and technical metadata.
Chachamaru127Implement features from Plans.md with tests in a Next.js/TypeScript stack.
YeaChan05Analyze codebases read-only and return ranked evidence-based syntheses with file references.
JaCha00Analyze repository codebases and return ranked findings with confidence levels.
