manage-error-debugging
Skill38 starsChanged 2 months agoMITView on GitHub
Manage Error Debugging Automation
In this repository101 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .cursor/rules/autonomous_execution.mdcCursor rule
- .cursor/rules/cursor_rules_editing.mdcCursor rule
- .cursor/rules/cursor_rules_sync.mdcCursor rule
- .cursor/rules/cursor_rules_sync_requirement.mdcCursor rule
- site_pages/llms.txtllms.txt
- advisorySkill
- analyzeSkill
- auditSkill
- commitSkill
- create-planSkill
- create_planSkill
- create-prototypeSkill
- create_prototypeSkill
- create_prSkill
- create-releaseSkill
- create_releaseSkill
- create-ruleSkill
- create_ruleSkill
- debugSkill
- draft-illustrationSkill
- draft_illustrationSkill
- endSkill
- evaluate_positioningSkill
- final-reviewSkill
- final_reviewSkill
- fix-feature-bugSkill
- fix_feature_bugSkill
- learnSkill
- manage_error_debuggingSkill
- neversight_learn_skills.dev_obviously_awesomeSkill
- process_issuesSkill
- process_prsSkill
- publish-planSkill
- publish_planSkill
- publishSkill
- pullSkill
- pushSkill
- recover_sqlite_databaseSkill
- releaseSkill
- report-errorSkill
- report_errorSkill
- reportSkill
- reviewSkill
- run-feature-workflowSkill
- run_feature_workflowSkill
- setup-commandsSkill
- setup_commandsSkill
- setup-cursor-copiesSkill
- setup_cursor_copiesSkill
- store-neotomaSkill
- store_neotomaSkill
- sync-env-from-1passwordSkill
- sync_env_from_1passwordSkill
- analyzeSkill
- auditSkill
- commitSkill
- create-planSkill
- create-prototypeSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. About 0 are common, 20 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈20
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 46
Check for PID file: .cursor/error_reports/watcher.pid
- Distinctive: line 47
If PID file exists, verify process is still running
- Distinctive: line 48
If running, exit with message: "Error debugging watcher is already running (PID: {pid})"
- Distinctive: line 53
If disabled, exit with error
- Distinctive: line 57
Ensure log directory exists (if configured)
- Very specific: line 62
Write PID to .cursor/error_reports/watcher.pid
- Distinctive: line 67
Check if process is still running
- Distinctive: line 68
If not running, read log file and show error
- Very specific: line 73
Read PID from .cursor/error_reports/watcher.pid
- Distinctive: line 74
If PID file doesn't exist, exit: "Error debugging watcher is not running"
- Distinctive: line 77
Check if process with PID is running
- Distinctive: line 78
If not running, remove stale PID file and exit: "Watcher process not found (stale PID file removed)"
- Distinctive: line 82
Wait up to 5 seconds for graceful shutdown
- Distinctive: line 83
If still running, send KILL signal
- Distinctive: line 91
If not found: "Status: Not running"
- Distinctive: line 94
Verify process with PID exists
- Distinctive: line 95
If not: "Status: Not running (stale PID file)"
- Distinctive: line 96
Remove stale PID file
- Distinctive: line 108
If not found: "No log file found.
- Distinctive: line 124
Remove PID file on stop or if process not found
- Very specific: line 139
Use ps command (available on macOS, Linux)
- Distinctive: line 183
If watcher fails to start, show error from log file
- Distinctive: line 184
If PID file exists but process not found, clean up stale PID file
- Distinctive: line 185
If configuration disabled, prevent start and show message
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Source: foundation/.cursor/skills/manage-error-debugging/SKILL.md -->name: manage-error-debugging description: Manage error debugging per foundation command. triggers:
- manage error debugging
- /manage_error_debugging
- manage-error-debugging
Manage Error Debugging Automation
Manage the error debugging automation monitoring script (start, stop, status, logs).
Command Usage
/manage_error_debugging [action]Actions:
start- Start the error debugging watcher in backgroundstop- Stop the running watcherstatus- Check if watcher is running and show statuslogs- Show recent logs from the watcherrestart- Stop and start the watcher- (no action) - Show status (default)
Prerequisites
- Error debugging automation enabled in
foundation-config.yaml scripts/trigger_error_debug_cli.jsexists and is executable- Node.js installed
Workflow
Action: start
- Check if already running:
- Check for PID file:
.cursor/error_reports/watcher.pid - If PID file exists, verify process is still running
- If running, exit with message: "Error debugging watcher is already running (PID: {pid})"
- Check for PID file:
- Verify configuration:
- Load
foundation-config.yaml - Check
development.error_debugging.enabled === true - If disabled, exit with error
- Load
- Create necessary directories:
- Ensure
.cursor/error_reports/exists - Ensure log directory exists (if configured)
- Ensure
- Start watcher in background:
- Run:
node scripts/trigger_error_debug_cli.js --watch > .cursor/error_reports/watcher.log 2>&1 & - Capture PID of background process
- Write PID to
.cursor/error_reports/watcher.pid - Output: "Started error debugging watcher (PID: {pid})"
- Run:
- Verify start:
- Wait 1 second
- Check if process is still running
- If not running, read log file and show error
Action: stop
- Check if running:
- Read PID from
.cursor/error_reports/watcher.pid - If PID file doesn't exist, exit: "Error debugging watcher is not running"
- Read PID from
- Verify process exists:
- Check if process with PID is running
- If not running, remove stale PID file and exit: "Watcher process not found (stale PID file removed)"
- Stop process:
- Send TERM signal to process
- Wait up to 5 seconds for graceful shutdown
- If still running, send KILL signal
- Remove PID file
- Output: "Stopped error debugging watcher (PID: {pid})"
Action: status
- Check PID file:
- Read
.cursor/error_reports/watcher.pid - If not found: "Status: Not running"
- Read
- Check if process is running:
- Verify process with PID exists
- If not: "Status: Not running (stale PID file)"
- Remove stale PID file
- If running, show:
- PID
- Uptime (how long it's been running)
- Configuration status (enabled/disabled)
- Last log entry (if log file exists)
Action: logs
- Check log file:
- Read
.cursor/error_reports/watcher.log - If not found: "No log file found. Watcher may not have started yet."
- Read
- Display logs:
- Show last 50 lines (configurable)
- Or tail logs if
--followflag provided
Action: restart
- Run stop action (if running)
- Wait 1 second
- Run start action
Implementation Notes
PID File Management:
- Store PID in:
.cursor/error_reports/watcher.pid - Remove PID file on stop or if process not found
Log File:
- Logs written to:
.cursor/error_reports/watcher.log - Rotate or truncate on restart (optional)
Process Verification:
# Check if process exists (cross-platform)
if ps -p $PID > /dev/null 2>&1; then
# Process is running
fiPlatform-Specific:
- Use
pscommand (available on macOS, Linux) - On Windows, may need
tasklistor PowerShellGet-Process
Configuration
Configure in foundation-config.yaml:
development:
error_debugging:
enabled: true
automation:
watch_mode: true # Enable continuous monitoring
cursor_cli:
# ... cursor_cli configuration ...Examples
# Check status
/manage_error_debugging
/manage_error_debugging status
# Start watcher
/manage_error_debugging start
# Stop watcher
/manage_error_debugging stop
# View logs
/manage_error_debugging logs
# Restart watcher
/manage_error_debugging restartRelated Commands
/report- Report an error (triggers debugging if automation enabled)/debug- Manually debug pending errors (deprecated: use/debuginstead)
Error Handling
- If watcher fails to start, show error from log file
- If PID file exists but process not found, clean up stale PID file
- If configuration disabled, prevent start and show message
- On stop, handle graceful shutdown with timeout fallback to KILL
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

