skills.rest
ahliweb
ahliwebCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

diagnose

Trace reproduced symptoms to the source code causing them.

Updated Aug 23, 2026
Search Tags:#debugging#troubleshooting#regression#root-cause#stack-trace#source-code
One-click install
npx skills add https://github.com/ahliweb/sikesra --skill diagnose-ahliweb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/ahliweb/sikesra/tree/main/awcmsmicro-dev/.flue/skills/diagnose
Command: npx skills add https://github.com/ahliweb/sikesra --skill diagnose-ahliweb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you trace a reproduced symptom, such as a failing test, console error, wrong response, or broken UI state, back to the exact source code that causes it.

Core Features & Use Cases

  • Pinpoints the specific file and approximate line responsible for the behavior.
  • Reads the relevant function, route, component, or migration in full to explain why the issue occurs.
  • Useful for debugging regressions, permission checks, pagination bugs, locale issues, and schema or migration failures.

Quick Start

Analyze the reproduced symptom and identify the most likely source file, line range, and confidence level.

Frequently Asked Questions about diagnose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace a stack trace back to the source code causing the error?▼

To trace a stack trace to its source code, you analyze the reproduced symptom, read the relevant function or component in full, and pinpoint the exact file and approximate line responsible for the behavior.

What is the best way to troubleshoot a database migration or schema regression?▼

Troubleshooting a schema regression involves reading the relevant migration file in full to explain why the issue occurs, identifying the specific file and line range responsible, and assigning a confidence level to the root-cause analysis.

Can I use this to debug a broken UI rendering state?▼

Yes, you can debug broken UI rendering by tracing the reproduced symptom back to the exact source code that causes it. It reads the relevant component or route in full to explain why the broken state occurs.

How do I find the root-cause of a failing test in my codebase?▼

Finding the root-cause of a failing test requires analyzing the reproduced symptom, carefully reading the relevant function or route, and providing precise file and line estimates with honest confidence ratings to explain the failure.

Does root-cause debugging work for wrong API responses and pagination bugs?▼

Yes, root-cause debugging works for wrong API responses and pagination bugs by tracing the reproduced symptom to the specific source code that causes it, reading the relevant route or function in full to explain the behavior.

What are the limitations of troubleshooting regressions without reading the full function?▼

Troubleshooting regressions without reading the full function limits diagnostic accuracy, because this approach requires careful reading of the relevant function, route, component, or migration in full to provide honest confidence ratings and precise file estimates.

Related Skills

Explore More Software Engineering Skills→
rakibulismrakibulism
2

debugger

Diagnose software bugs from errors, stack traces, logs, and failing tests.

Community
Advanced
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
Ramprasad4121Ramprasad4121
1

variant-analysis

Search codebases for patterns matching known vulnerabilities and bugs.

Community
Advanced
chicanoandres702chicanoandres702

error-detective

Correlate logs, stack traces, and anomalies to diagnose distributed system errors.

Community
Advanced