Analyzes architecture, bugs, dependencies across files, logs, and runtime traces to identify root causes.
npx skills add https://github.com/pextacy/stellar --skill analyze-pextacy
Please help me install this Agent Skill. Skill: analyze Source: https://github.com/pextacy/stellar/tree/main/skills/analyze Command: npx skills add https://github.com/pextacy/stellar --skill analyze-pextacy
Helps analysts and engineers diagnose ambiguous, causality-driven questions by structuring observations, testing hypotheses, and weighing evidence across multiple sources to identify root causes.
Provide a structured investigation by listing observations, formulating hypotheses, gathering evidence, and stating the current best explanation.
High-intent search queries and answers about installing and using this skill.
Root-cause analysis across scattered code, logs, and configs requires formalizing observations, ranking hypotheses, and weighing evidence. This Skill integrates cross-file findings to output a most likely explanation and a recommended next step.
Structuring an investigation for ambiguous bugs involves cataloging observations, formulating hypotheses, and mapping evidence for and against each. This approach yields ranked hypotheses and identifies critical unknowns for targeted probing.
Evidence-driven hypothesis testing is needed when architecture analysis requires cross-file reasoning over dispersed artifacts. It formalizes current best explanations by validating hypotheses against runtime traces and configuration evidence.
Yes, investigating dependency issues and runtime traces fits this approach by correlating dispersed evidence. It evaluates evidence for and against hypotheses to determine the most likely explanation and recommend a discriminating probe.
Root-cause investigations fail when they lack structured evidence weighing and ignore critical unknowns. Formalizing hypotheses against cross-file evidence gaps ensures a discriminating probe is identified to validate the most likely explanation.
No specific dependencies or components are required. The method applies structured reasoning to existing artifacts like code, configs, and logs to produce evidence summaries and recommended next steps.
hendrax5Returned successfully.
xdkpTrace ambiguous causal questions to identify the most likely explanation.
bonjohenGenerate architecture and evidence-graph diagrams from a project knowledge graph.
Pjpj42Diagnose iOS Swift software issues by inspecting logs and code.
