Add debugging failed tests section to TeaPie skill

[Burgyn]

Summary

• Add escalating diagnostic workflow section to the TeaPie Claude skill for handling test failures
• Step 1: Re-run with --requests-log-file to capture full HTTP request/response details (JSONL format)
• Step 2: Re-run with debug/verbose logging (-d, -v, --log-file) for framework-level diagnostics
• Step 3: Structured analysis — identify root cause, explain clearly to user, suggest concrete fix
• Includes combined diagnostic command for maximum information in a single run

Test plan

• Invoke the teapie skill in Claude Code and verify the new "Debugging Failed Tests" section is loaded
• Verify --requests-log-file and logging flags match current TeaPie CLI options
• Simulate a test failure scenario and confirm the skill guides the agent through the diagnostic workflow

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Added comprehensive debugging guide for failing tests, including escalating diagnostic steps with request/response logging, enhanced framework logging options, and root cause analysis guidance to help troubleshoot test failures effectively.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 87a45443-7974-41cd-ae79-a16f3a9ce77d

📥 Commits

Reviewing files that changed from the base of the PR and between 3a4d6e2 and 9b7feda.

📒 Files selected for processing (1)

• .claude/skills/teapie/SKILL.md

---

📝 Walkthrough

Walkthrough

Added a "Debugging Failed Tests" documentation section to TeaPie's SKILL.md defining an escalating diagnostic workflow. It covers re-running tests with --requests-log-file to capture HTTP details, enabling verbose/debug logging with -d/-v flags, and performing root cause analysis with gathered logs.

Changes

Cohort / File(s)	Summary
TeaPie Debugging Documentation .claude/skills/teapie/SKILL.md	New "Debugging Failed Tests" section documenting a three-step escalating workflow: (1) re-run with --requests-log-file to inspect HTTP request/response details, (2) re-run with debug/verbose logging flags and optional --log-file, and (3) analyze logs to identify root cause and suggest fixes. Includes example command combining all diagnostic options.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰✨ A carrot for clarity, a hop through the logs!
When tests go astray, we debug through the fog,
With requests and verbosity, step by tiny step,
Even the trickiest bugs can't outrun our prep! 🥕🔍

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch debbuginginfo

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}