Bug report to merged PR in one chainin 5 steps
Turn a Linear bug ticket into a tested fix on main without hunting through dashboards.
The steps and the skill for each
- 1Linear MCP Server
Pull the bug report's full context, repro steps, and any prior debugging comments.
- 2GitHub MCP Server
Locate the offending file, recent commits, and any related PRs or issues.
- 3Debugging And Error Recovery
Diagnose the root cause systematically and implement the fix.
- 4Playwright MCP Server
Add a regression test that fails before the fix and passes after — proof the bug stays dead.
- 5Sentry MCP Server
After deploy, confirm the error rate dropped and close the loop on the original ticket.
The kit behind it all 6 skills for testing & qa
This workflow uses skills from the Testing & QA kit. The kit has the full set for the field, in the order to install them.
More workflows for developers
All workflowsBuild a UI feature that holds up
Six steps, from ticket to a reviewed PR
- 01Read the ticket and the codebase
- 02Build it on the system
- 03First render
- +3 more steps
Ship a feature end-to-end with a coding agent
From an empty repo branch to a deployed preview link with passing tests and a clean PR description.
- 01Context7
- 02Test Driven Development
- 03Supabase MCP Server
- +2 more steps
Harden a feature before release
Review a change for security issues, check dependencies and test it in a real browser before it ships.
- 01Security And Hardening
- 02Differential Security Review
- 03Cve MCP Server
- +2 more steps