Harden a feature before releasein 5 steps
Review a change for security issues, check dependencies and test it in a real browser before it ships.
The steps and the skill for each
- 1Security And Hardening
Audit input handling, auth and data storage for vulnerabilities.
- 2Differential Security Review
Run a security-focused review of the diff with git history context.
- 3Cve MCP Server
Look up known CVEs and exploit scores for the dependencies you touch.
- 4Web App Testing
Exercise the feature in a real browser with Playwright.
- 5Shipping And Launch
Walk the pre-launch checklist: monitoring, rollback and flags.
The kit behind it all 6 skills for security
This workflow uses skills from the Security 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
Bug report to merged PR in one chain
Turn a Linear bug ticket into a tested fix on main without hunting through dashboards.
- 01Linear MCP Server
- 02GitHub MCP Server
- 03Debugging And Error Recovery
- +2 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