project-doctor

Aggregate module counts, file sizes, and architecture health signals to identify project gaps.

12|2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/toly1994328/flash_im_by_ai --skill project-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-doctor
Source: https://github.com/toly1994328/flash_im_by_ai/tree/main/.kiro/skills/project-doctor
Command: npx skills add https://github.com/toly1994328/flash_im_by_ai --skill project-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill helps teams assess code quality, architecture health, and overall reliability by performing a structured health check across frontend and backend workstreams. It identifies hotspots, potential risks, and provides actionable remediation guidance.

Core Features & Use Cases

  • Six-step health check workflow (望、闻、问、切、治、沉) to systematically inspect module structure, static analysis results, and code health.
  • Automated generation of dedicated health reports under docs/project/checkup/{tag}/{端}/01_望_结构统计.md and related outputs, enabling traceable audits.
  • Remediation planning and collaboration assistance to propose fixes, track progress, and improve long-term maintainability.

Quick Start

Run the six-step health check by executing the provided checkup scripts to generate diagnostic reports and start remediation planning.

Frequently Asked Questions about project-doctor

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

FAQPage Schema
How do I diagnose code quality and architecture health for my web application?

Project health diagnosis requires aggregating module counts, file sizes, and architecture signals to identify hotspots. A six-step automated health check workflow systematically inspects frontend and backend workstreams to detect structural risks and provide remediation guidance.

What's the best way to automate static analysis and remediation planning during release cycles?

Static analysis and remediation planning are automated by running dedicated checkup scripts that generate diagnostic reports. These reports trace module structure and code health issues, enabling teams to propose fixes and track progress during development and release cycles.

When do I need an architecture review and automated project health check?

An architecture review and project health check is needed when assessing code quality, reliability, and maintainability across frontend and backend workstreams. It identifies potential risks and hotspots before they impact long-term maintainability during development or release audits.

Can I use this to perform a code review audit for both frontend and backend at the same time?

Code review audits can be performed simultaneously for frontend and backend workstreams. The system applies modular data collection and static analysis to both sides, generating dedicated health reports under traceable output paths for comprehensive architecture review.

How does the six-step health check workflow generate traceable audit reports?

The six-step health check workflow generates traceable audit reports by executing checkup scripts that output diagnostic markdown files. These files are structured under specific project checkup directories, capturing structural statistics and code review insights for each tag and workstream.

Does project health monitoring work without integrating external static analysis dependencies?

Project health monitoring operates without external dependencies by aggregating module counts and file sizes internally. It calculates architecture health signals directly from the existing project structure to identify hotspots and guide remediation planning.