source-command-debug

Diagnose issues by investigating logs, SQLite database state, and git history.

1|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/redblacktree/fastflow --skill source-command-debug-redblacktree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-debug
Source: https://github.com/redblacktree/fastflow/tree/main/.agents/skills/source-command-debug
Command: npx skills add https://github.com/redblacktree/fastflow --skill source-command-debug-redblacktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When manual testing or implementation goes wrong, developers need to investigate logs, database state, and recent code changes without burning the primary session's context. This Skill bootstraps a focused debugging session that gathers evidence from multiple sources and produces a structured root-cause report. ## Core Features & Use Cases - Parallel Investigation: Spawns concurrent Task agents to analyze daemon and WUI logs, query the SQLite database, and inspect git state simultaneously. - Structured Debug Report: Presents findings with evidence from logs, database queries, and git diffs, plus a root-cause hypothesis and concrete next steps. - Read-Only Investigation: Examines system state without editing files, keeping the debugging session safe and isolated. - Use Case: During manual testing a session appears stuck. Invoke this Skill, describe the symptom, and it checks recent logs for errors, queries the sessions table for stuck states, and reviews uncommitted changes to pinpoint the cause. ## Quick Start Ask the agent to debug the current issue by describing what went wrong and letting it investigate the logs, database, and git state.

Frequently Asked Questions about source-command-debug

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

FAQPage Schema
How do I debug issues using logs and database state?▼

Describe the problem you encountered, and the Skill spawns parallel investigations of recent logs, the SQLite database, and git state. It then presents a debug report with evidence, a likely root cause, and specific next steps to try.

How to query SQLite database for debugging session state?▼

Use sqlite3 against the daemon database to inspect tables like sessions and conversation_events. Example queries include listing recent sessions ordered by creation time and filtering events from the last hour to find stuck or anomalous states.

Can this debugging approach edit or fix files automatically?▼

No, the investigation is strictly read-only. It examines logs, database records, and git history to identify the root cause, then suggests commands or actions for you to run, such as restarting services or enabling debug mode.

What are the limitations of log-based debugging?▼

Some issues fall outside its reach, including browser console errors, MCP server internal state, and system-level problems. For those cases it directs you to check browser developer tools or investigate the affected component directly.

Why does debugging require a problem description first?▼

Investigation cannot proceed without knowing what went wrong, since logs and databases contain large amounts of unrelated data. A symptom description, expected behavior, and timeframe let the parallel agents filter evidence to the relevant window.