diagnose

Diagnose project issues by analyzing code and configurations.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/wutongshenqiu/prism --skill diagnose-wutongshenqiu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/wutongshenqiu/prism/tree/main/.agents/skills/diagnose
Command: npx skills add https://github.com/wutongshenqiu/prism --skill diagnose-wutongshenqiu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of diagnosing and fixing project issues, helping developers identify and resolve problems efficiently.

Core Features & Use Cases

  • Automated Diagnostics: Analyze problem descriptions to pinpoint likely problematic modules.
  • Code Examination: Read and analyze relevant source files and configurations.
  • Test Case Construction: Generate minimal test cases to reproduce issues.
  • Fix Implementation: Guide users to implement fixes and verify them.
  • Use Case: If you encounter a routing issue in your project, this Skill can help you diagnose the problem, locate the relevant code, and guide you through the process of implementing a fix.

Quick Start

Use the diagnose skill to identify the root cause of a routing issue in your project.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I diagnose the root cause of a routing issue in my project code?

To diagnose project issues, you must provide a clear problem description and grant access to your project's source code and configurations. The skill examines these inputs to pinpoint problematic modules and generates minimal test cases to reproduce the exact software development errors.

What is the best way to automate troubleshooting for streaming and configuration problems?

Automating troubleshooting for streaming and configuration problems involves analyzing issue descriptions and examining relevant code. This skill automates this process by reading source files, constructing test cases to reproduce the configuration or streaming behavior, and guiding the fix implementation.

Can I resolve translation issues by examining source files and configurations directly?

Yes, you can resolve translation issues by reading and analyzing relevant source files and configurations. This skill diagnoses the project problem by locating the translation code, generating a minimal test case to reproduce the error, and guiding you to implement the fix.

Does automated code analysis work without access to the full project code?

No, automated code analysis for diagnosis requires access to your project code and configurations to examine the relevant source files. Without this access, the skill cannot read the code, construct minimal test cases, or guide you through implementing the required fix.

Why does my project troubleshooting workflow fail to pinpoint the problematic module?

Project troubleshooting fails to pinpoint problematic modules when the problem description lacks sufficient detail for code analysis. Providing a clear issue description and granting access to project configurations allows the diagnostic process to locate the relevant code and reproduce the error.