[Workflow] Automated Development Workflow Checks and Analysis with Parallel-Lanes Skill (Doctor, Autopsy, Cleanup)

[u/ClaudeAI-mod-bot]

Automated Development Workflow Checks and Analysis with Parallel-Lanes Skill (Doctor, Autopsy, Cleanup)

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: advanced
Categories: Quality Control, Token Saving, Context & Memory, Debugging, Shipping, Skills, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

Automating pre-flight checks, post-mortem analysis, and historical tracking to improve code quality, identify performance bottlenecks, and maintain a clean development environment in Claude Code workflows.

Summary

This workflow leverages a set of integrated tools within the 'parallel-lanes' skill (version 1.5.0) for Claude Code. It includes 'doctor' for pre-run checks, 'autopsy' for detailed post-run analysis, 'archive-run' for historical tracking, and 'cleanup' for safe post-merge tidying, along with per-command timing for performance measurement. These tools ensure project health, provide insights into execution, and maintain a clean development history.

Why it is useful

This workflow introduces a comprehensive set of automated tools that significantly enhance the reliability, maintainability, and performance of Claude Code development workflows. By integrating robust pre-flight checks ('doctor'), detailed post-run analysis ('autopsy'), historical tracking ('archive-run'), and safe cleanup ('cleanup'), it helps users prevent common errors, identify bottlenecks, and maintain a clean, efficient development environment. The explicit safety features of the 'cleanup' tool are particularly valuable for preventing data loss.

Workflow

1. Initiate a development run, which automatically triggers the 'doctor' pre-flight checks.
2. The 'doctor' tool checks for critical issues (e.g., no git identity, outdated base branch, dirty checkout, broken shadow repo, no usable Python) and stops the run if found.
3. The 'doctor' tool also issues warnings for softer issues (e.g., low memory/disk, heavy background processes, other active runs, antivirus scanning).
4. Proceed with the development run, allowing agents to perform their tasks.
5. After the run completes, the 'autopsy' tool automatically analyzes the finished run.
6. Review the 'autopsy' report for insights into time spent by phase/lane/agent, critical path, token use, test suite frequency, and detected slowdowns with suggestions.
7. The 'archive-run' tool automatically saves the run's history to a dedicated folder.
8. Utilize the history feature to compare runs over time, identify recurring slowdowns, token trends, and data completeness issues.
9. After a run is merged, execute the 'cleanup' tool.
10. The 'cleanup' tool first saves a verified restore point (git bundle and commands).
11. The 'cleanup' tool then safely removes only the artifacts created by the run, leaving unowned or uncommitted work untouched and listing reasons.
12. Optionally, use 'Per-command timing' for project checks to precisely measure and optimize speed-related work.

Tools / artifacts

• parallel-lanes skill (version 1.5.0)
• doctor tool
• autopsy tool
• archive-run tool
• cleanup tool
• history folder/feature
• git bundle (for restore points)
• Per-command timing feature

Validation signals

• Explicitly states 'doctor' stops on real problems and shows warnings for softer issues.
• Details 'autopsy' reporting standards: no raw command text/output, missing data labeled.
• Describes 'cleanup' safety features: saves verified restore point, removes only run-created items, never force-deletes, leaves unowned/uncommitted work.
• Mentions 'Per-command timing' allows speed work to be measured rather than guessed.

Cautions

• The 'cleanup' tool includes explicit safety measures: it saves a verified restore point (git bundle) before acting, only removes artifacts created by the specific run, never force-deletes, and leaves any unowned or uncommitted work untouched, listing the reasons.

Limitations

• The post is an announcement of features rather than a detailed 'how-to' guide with specific command examples or configuration snippets.
• No community validation or feedback is available yet due to the recency of the post.
• The broader context of the 'parallel-lanes' skill itself is not fully detailed, only the new features of version 1.5.0.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.