Analyze codebases to rank evidence-based explanations of behaviors and failures.
npx skills add https://github.com/zchee/json-repair-rs --skill analyze-zchee
Please help me install this Agent Skill. Skill: analyze Source: https://github.com/zchee/json-repair-rs/tree/main/.codex/skills/analyze Command: npx skills add https://github.com/zchee/json-repair-rs --skill analyze-zchee
This Skill helps users understand complex codebases by providing grounded, read-only analysis that ranks possible explanations with confidence levels, aiding in informed decision-making.
Ask the analyze skill to review the repository and clarify its architecture or behaviors before making changes.
High-intent search queries and answers about installing and using this skill.
To analyze a codebase and find a bug, this Skill examines multiple files, traces code paths, and evaluates evidence to provide ranked hypotheses of the most probable causes. It prioritizes explanations by supporting code evidence to aid debugging.
Evidence-based codebase analysis is a read-only process that clarifies repository architecture and behaviors by tracing code paths across multiple files. It provides grounded insights into structural decisions to support informed development planning.
Yes, you can safely understand repository behaviors without modifying code because the Skill performs strictly read-only, non-intrusive analysis. It comprehends complex codebases by evaluating evidence without executing or altering the existing code structure.
This approach ranks explanations for codebase failures by evaluating supporting evidence across multiple files and tracing execution paths. It assigns confidence levels to each hypothesis, helping developers identify the most likely architectural or behavioral causes.
The best way to review unfamiliar repository architecture is to request a grounded, read-only analysis that traces code paths and explains structural decisions. This provides ranked insights into behaviors and contracts, ensuring informed decisions before modifications.
A limitation of analyzing code paths for debugging is that the process is strictly read-only and does not execute the code, meaning dynamic runtime failures might not be fully captured. It relies on static structural evidence to rank behavioral hypotheses.
rajyeole6Analyze repository structure and execution paths to generate orientation maps.
kyo0221Guide a 6-phase workflow to reproduce, diagnose, and fix software bugs.
chriswesttIdentify bug root causes through symptom collection, code path tracing, and deterministic reproduction.
RamblurrCapture and inspect Clojure function local scope at runtime.
