diagnose

Inspect codebases and draft bug specifications for GitHub issues.

1|Updated Feb 10, 2026

Search Tags:#automation #investigation #github #diagnose #triage #bug #spec-generation

Ready to run

npx skills add https://github.com/opsMachine/OM-Agency --skill diagnose-opsmachine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/opsMachine/OM-Agency/tree/main/skills/diagnose
Command: npx skills add https://github.com/opsMachine/OM-Agency --skill diagnose-opsmachine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates bug triage by taking triage context, inspecting the codebase, and generating a draft bug specification to begin remediation without manual back-and-forth.

Core Features & Use Cases

Triage-driven investigation: Gathers context from the workflow manager and identifies potential root causes.
Draft spec generation: Produces a ready-to-review bug spec saved to Documents/specs with an Approved status.
Security checks: Performs a quick security assessment to flag high-risk issues for extra review.

Quick Start

Provide triage context to the diagnose agent to initiate root-cause analysis and draft a bug spec.

Frequently Asked Questions about diagnose

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

FAQPage Schema

How do I automate bug triage for GitHub issues?▼

You can automate bug triage by feeding triage context to an agent that inspects your codebase and drafts a bug specification. It reads the issue, investigates the code, runs security checks, and outputs an Approved spec for remediation handoff.

What is automated bug spec generation and how does it work?▼

Automated bug spec generation takes triage context, inspects the codebase to find root causes, and drafts a ready-to-review bug specification. The final spec is saved to Documents/specs with the Status set to Approved for implementation teams.

Can I triage untracked bug reports without an existing GitHub issue?▼

Yes, triage applies to both tracked GitHub issues and untracked reports. You provide the triage context, and the system investigates the codebase to guide root-cause discovery and generate a draft specification for the reported bug.

Do I need repository access to run automated codebase investigation for bugs?▼

Yes, repository access is required for code inspection, issue context gathering, and writing the final bug spec. Access enables the agent to read the codebase, identify potential root causes, and save the Approved specification to Documents/specs.

Does automated bug triage include security checks?▼

Yes, automated bug triage performs a quick security assessment during the investigation. It flags high-risk issues for extra review before drafting the final bug specification, ensuring security concerns are identified during root-cause discovery.