Week 3 · Track split, deeper
Day 10
Extend, automate, review
Review and quality
/code-reviewon a real branch; then ultrareview (/code-review ultra) on a seeded-buggy branch (the lead prepares one) — compare signal.- Security plugins walkthrough (
security-guidance, Claude Security scan).
Exercise
Fix what the review found; PR green; note false positives for the retro.
Automated testing
CI and triage
- Tests run on PRs via GitHub Actions; triage one seeded red build with Claude ("regression, flaky, or environment?").
/loop 15m watch the runbabysitting; artifact test report (pass/fail by area, flaky list) shared to the channel.- BA: release-notes drafting with Claude from the merged PRs; publish as an artifact.
Skills today
Developer track
- /loop: Scheduled re-runs: watch a PR, babysit CI, morning maintenance
How to set up
See Day 6 for the setup steps.
- ultrathink + /effort levels: Deep reasoning spent only where it pays (the “ultracode” ask in real form)
How to set up
See Day 6 for the setup steps.
- /code-review → ultrareview: Catch what tired humans miss; multi-agent cloud review for risky branches
How to set up
Already built in — type
/code-reviewin a Code session for a review of your changes;/code-review ultraescalates to the deeper multi-agent cloud review (needs a claude.ai account). - Security plugins (security-guidance, Security scan): Claude reviews its own changes for security issues
How to set up
Already built in — type
/security-reviewbefore committing to scan for vulnerabilities. Extra security plugins:/plugin→ Discover tab → search the name your team uses (e.g. security-guidance, Security scan) → install. - review-checklist skill: The Day-3 checklist becomes enforced practice
How to set up
See Day 3 for the setup steps.
BA/QA track
- CI triage (“regression, flaky, or environment?”): One sentence of root cause from a red build
How to set up
Nothing to install — paste the red build's log into a Claude session and ask "regression, flaky, or environment?" One sentence of root cause comes back.
- Release notes from merged PRs (artifact): Client-facing value visible in minutes
How to set up
Nothing extra to install — in a Code session ask: "draft release notes from the merged PRs as an artifact" (see Artifacts, Day 06).
Related: Course catalog · Developer track · BA/QA track · Shared fundamentals