Diagnose software bugs and commit minimal corrective code changes.
npx skills add https://github.com/Srajangpt1/dataeye --skill dev-debug-srajangpt1
Please help me install this Agent Skill. Skill: dev-debug Source: https://github.com/Srajangpt1/dataeye/tree/main/packages/browseros-agent/.claude/skills/dev-debug Command: npx skills add https://github.com/Srajangpt1/dataeye --skill dev-debug-srajangpt1
A structured, repeatable workflow for diagnosing software issues, identifying the most probable root causes, implementing minimal fixes, testing them, and committing changes so developers can resolve bugs efficiently and with audit trails.
Invoke the skill with /dev-debug followed by a concise description of the issue to generate the debug directory, a ranked root-cause analysis, and a proposed minimal fix.
High-intent search queries and answers about installing and using this skill.
To debug a failing integration test, you trace relevant code paths to generate a ranked list of 2–5 probable root causes. This root-cause analysis is recorded in a temporary markdown file before applying fixes.
The best way to fix software bugs without broad refactors is to implement minimal, pattern-consistent code changes. This targeted approach ensures the corrective fix directly addresses the identified root cause.
Yes, you need a git workspace to commit code fixes during debugging. The workflow requires access to the project source and a git workspace to stage and commit the applied minimal fixes with a clear message.
Root-cause analysis for CI-failure investigations works by diagnosing software issues, identifying probable causes, and recording the analysis in a debug directory. This creates an audit trail for local development and CI scenarios.
To test and commit minimal code fixes, you run existing tests or define manual test steps to validate the change. Once verified, you stage and commit the fixes to your git workspace with a clear commit message.
You should not use a structured debugging workflow for code fixes if your scenario lacks access to the project source or a git workspace. This workflow specifically requires reproducing steps, tracing code paths, and committing fixes.
rishikanthcCreate isolated git worktrees with dependency setup and baseline test verification.
aist-ai-sastDiagnose MCP regression failures and implement durable fixes across test suites.
frizzle-chanAnalyze test output, plan fixes, and re-run tests until all pass.
nicolanoviellReview code changes for bugs, style issues, and best practices.
