ai-dev-tools-debug

Reproduce and inspect AIDevTools issues across repositories, eval data, and logs.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/gestrich/AIDevTools --skill ai-dev-tools-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-dev-tools-debug
Source: https://github.com/gestrich/AIDevTools/tree/main/.agents/skills/ai-dev-tools-debug
Command: npx skills add https://github.com/gestrich/AIDevTools --skill ai-dev-tools-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, safe way to reproduce, inspect, and troubleshoot issues in the AIDevTools evaluation, planning, and Mac app workflow by exposing access to repositories, eval cases, artifacts, and log data for debugging sessions.

Core Features & Use Cases

  • Guided discovery and debugging workflows across eval systems, plan runner, and the macOS app.
  • Reproduction of user-reported bugs by locating repos, cases, artifacts, and plan logs to verify fixes and reproduce failures.
  • Safe, read-only guidance with CLI commands and checks to diagnose problems without altering user data.

Quick Start

Reproduce a reported issue by listing repos, locating the target repo paths, and inspecting artifacts and plan logs to identify the root cause.

Frequently Asked Questions about ai-dev-tools-debug

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

FAQPage Schema
How do I debug AI evaluation failures using logs and artifacts?

You can debug AI evaluation failures by accessing repositories, eval data, artifacts, and logs through the CLI and app workflows. This skill provides guided discovery and read-only inspection to help you reproduce issues and identify root causes across multiple environments.

What is the best way to reproduce a reported bug in an AI eval system?

The best way to reproduce a reported bug is to list repositories, locate the target repo paths, and inspect artifacts and plan logs. This structured workflow verifies fixes and reproduces failures safely without altering user data.

Can I inspect plan logs and artifacts without modifying user data?

Yes, you can inspect plan logs and artifacts without modifying user data. This skill provides safe, read-only guidance with CLI commands and checks to diagnose problems across eval systems, plan runners, and the macOS app.

How do I troubleshoot issues across multiple AI repositories and environments?

Troubleshoot issues across multiple repositories and environments by using coordinated discovery and read-only inspection workflows. The skill exposes access to eval cases, artifacts, and log data to help you debug across the eval system, plan runner, and macOS app.

Does this debugging workflow support the macOS app and plan runner?

Yes, this debugging workflow supports the macOS app and plan runner. It provides guided discovery and debugging workflows across eval systems, the plan runner, and the macOS app to help you reproduce user-reported bugs and verify fixes.

What are the limitations of read-only CLI debugging for AI evaluations?

The limitation of read-only CLI debugging for AI evaluations is that it provides safe, read-only guidance to diagnose problems without altering user data. It coordinates discovery and inspection but does not directly apply fixes or modify repository state.