source-command-ff-debug

Investigate issues by analyzing 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-ff-debug-redblacktree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-ff-debug
Source: https://github.com/redblacktree/fastflow/tree/main/.agents/skills/source-command-ff-debug
Command: npx skills add https://github.com/redblacktree/fastflow --skill source-command-ff-debug-redblacktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When manual testing or implementation goes wrong, diagnosing the root cause requires digging through scattered logs, database records, and git changes, which consumes context and time. This Skill bootstraps a focused debugging session that investigates these sources without editing any files. ## Core Features & Use Cases - Parallel Log Investigation: Spawns Task agents to find and analyze the latest daemon and WUI logs under ~/.humanlayer/logs/ for errors, warnings, and stack traces. - Database State Inspection: Queries the SQLite daemon database directly with sqlite3 to check sessions, conversation events, and stuck states. - Git and Service State Analysis: Reviews current branch, recent commits, uncommitted changes, and verifies daemon/WUI processes and sockets are running. - Use Case: During manual testing a session stops responding. Invoke this Skill, describe the symptom, and receive a structured debug report with evidence from logs, database queries, and git state plus concrete next steps. ## Quick Start Ask the agent to debug the current issue by investigating recent logs, the daemon database, and git state, then describe the problem you encountered.

Frequently Asked Questions about source-command-ff-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, then the Skill spawns parallel investigation tasks that search recent daemon and WUI logs for errors, query the SQLite database for anomalous sessions or events, and check git state. Findings are compiled into a structured debug report.

How to check SQLite database state during debugging?▼

Connect directly with sqlite3 to the daemon database at ~/.humanlayer/daemon-{BRANCH_NAME}.db. Use .tables and .schema to inspect structure, then query recent sessions and conversation_events ordered by created_at to find stuck states or anomalies.

Can this debugging approach edit or fix files automatically?▼

No, this is a pure investigation workflow with no file editing. It only reads logs, queries the database, and inspects git state, then presents findings and suggested commands for you to run yourself.

What issues are outside the scope of log and database debugging?▼

Browser console errors, MCP server internal state, and system-level issues cannot be inspected directly. For those, check the browser console with F12 or restart services using make daemon and make wui.

Why does debugging require a problem description first?▼

Investigation cannot proceed without knowing what went wrong, when it last worked, and what was being tested. The description focuses log searches and database queries on the relevant timeframe and components.