chore: improve test-discovery skill with PR docs and TUI E2E guidance#365
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Disabled knowledge base sources:
📝 WalkthroughWalkthroughThe PR template in Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested labels
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
What does this PR do?
Updates the
/test-discoveryskill with two new rules and a revamped PR template, based on issues found during the first automated test sweep run.Changes
Revamped PR template (Phase 5)
The previous template produced low-quality one-liner descriptions like "Adds tests for [area] discovered by hourly test sweep." The new template requires:
New Rule 9 — TUI E2E impact check
When tests touch code that feeds into the TUI (session state, config, skills, tools, MCP, providers), the skill now requires checking whether the TUI could be affected and adding E2E tests for those paths. Points to
packages/opencode/test/config/tui.test.tsas a reference. TUI regressions are high-visibility since it's the primary user interface.New Rule 10 — PR documentation standard
Explicitly codifies that one-liner PR bodies are not acceptable. Every PR must explain what was tested, why, and what risk is mitigated.
Type of change
Issue for this PR
N/A — process improvement
How did you verify your code works?
Documentation-only change to a
.claude/commands/skill file. Verified markdown renders correctly.Checklist
https://claude.ai/code/session_01AkMKqcoyJ1vURZ4crtpEZu
Summary by CodeRabbit