diagnose

Analyzes a repository and creates validated GitHub issues without modifying code.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/hirokimry/vibecorp --skill diagnose-hirokimry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/hirokimry/vibecorp/tree/main/skills/diagnose
Command: npx skills add https://github.com/hirokimry/vibecorp --skill diagnose-hirokimry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual overhead of reviewing a codebase for improvement opportunities, then turning validated findings into GitHub Issues instead of leaving them as vague notes.

Core Features & Use Cases

  • Autonomous repository analysis: Scans the project for technical debt, product misalignment, and Claude Code specification drift.
  • Safety-first filtering: Applies multi-agent checks and guardrails so restricted areas, self-weakening changes, and other unsafe ideas are excluded.
  • Issue-ready output: Produces structured improvement candidates and prepares them for GitHub issue creation without changing any code.
  • Use case: Run a full-priority diagnosis on a complex repository when you want actionable improvement tickets, not a code rewrite.

Quick Start

Use the diagnose skill to analyze this repository, filter unsafe candidates, and prepare GitHub Issues for the best improvements without modifying code.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I automatically analyze a codebase for technical debt and create GitHub issues?

To automate codebase analysis for technical debt, you can run a full-priority diagnosis that scans source files, configuration, and hooks, then converts validated findings into structured GitHub Issues without modifying code.

What is autonomous codebase diagnosis and how does it work?

Autonomous codebase diagnosis is the process of scanning a repository to identify technical debt, product misalignment, and specification drift, applying multi-agent filtering and guardrails to exclude unsafe ideas before creating structured GitHub Issues.

How can I scan my repository for Claude Code specification drift safely?

You can scan for Claude Code specification drift safely by running a scope-limited diagnosis that applies preset verification, multi-agent checks, and guardrails to exclude restricted areas and self-weakening changes from the final issue output.

Can I generate GitHub issues from codebase analysis without modifying my source code?

Yes, you can generate GitHub Issues from codebase analysis without modifying source code by running a diagnosis that strictly separates issue discovery from implementation, ensuring the process only creates structured improvement tickets.

What's the best way to filter unsafe improvement candidates during a codebase review?

The best way to filter unsafe improvement candidates during a codebase review is to apply safety-first multi-agent filtering and enforce guardrails that automatically exclude restricted areas and self-weakening changes from issue creation.

Does autonomous codebase diagnosis work on configuration files and hooks, or just source files?

Autonomous codebase diagnosis works across full-priority targets including source files, configuration, hooks, and Claude Code integration assets, ensuring comprehensive scanning for improvement opportunities throughout the entire repository.