Diagnose codebase problems by inspecting files, git history, and test cases.
npx skills add https://github.com/Vekta/PolyForge --skill diagnose-vekta
Please help me install this Agent Skill. Skill: diagnose Source: https://github.com/Vekta/PolyForge/tree/main/skills/diagnose Command: npx skills add https://github.com/Vekta/PolyForge --skill diagnose-vekta
This Skill helps users pinpoint the root cause of software errors, unexpected behavior, or log entries, determining if it's a bug, configuration issue, or expected behavior.
NullPointerException in their application logs, they can use /diagnose to trace the error, understand its origin, and get a clear explanation of why it's happening and how to resolve it.Use the diagnose skill to investigate the error message "TypeError: Cannot read properties of undefined (reading 'name')".
High-intent search queries and answers about installing and using this skill.
To find the root cause of an unhandled exception, you investigate specific problems within your codebase by inspecting files and tracing git history. This determines the exact origin and classifies the error as a bug, configuration issue, or expected behavior.
The best way to troubleshoot unexpected behavior and log entries is to perform detailed error analysis through file inspection and test case correlation. This identifies the fundamental reason behind the problem and assesses its severity.
Yes, you can determine if an error is a bug or a configuration issue. By investigating the reported problem and analyzing its origin, the diagnostic process classifies the issue and provides actionable recommendations for resolving it.
To analyze a NullPointerException using git history and test cases, you investigate the specific error within the codebase. This correlates test cases with file changes to determine the root cause and severity of the exception.
Yes, error analysis provides actionable recommendations for fixing software bugs. After determining the root cause and severity of an issue, it suggests concrete next steps such as creating an issue ticket or attempting a code fix.
thechandanbhagatAnalyze stack traces and logs to identify root causes and suggest fixes.
edulazaroAnalyze Laravel stack traces and apply code fixes across controllers, models, and database layers.
tonombResolve git merge and rebase conflicts by analyzing commit history and reconciling code changes.
OneWave-AIReview code for security vulnerabilities, performance bottlenecks, and maintainability issues.