Add or change a tool, a tool's input schema or description, or the step, Maily email-body, skip-condition or payload-property schemas in apps/mcp-server (the hosted Novu MCP server, also shipped in process to the enterprise Copilot as @novu/mcp-server/tools).…
Post-implementation PR prep for Novu feature branches — quality passes, commit/PR hygiene, CI triage, and review feedback. Use after feature work is done, when the user asks to prepare a PR, ship a branch, fix CI, address review comments, or babysit a pull…
Implement planned work by fanning out parallel subagents on isolated worktrees — TDD at pre-agreed seams, per-slice nv-park-and-review, merge back, full suite once at the end.
Remove AI-generated code slop and clean up code style
Fetch and summarize review comments from the active pull request
Run e2e tests for the API service. Use when the user wants to run API E2E tests.
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
Build or refactor a Tool-channel provider (PagerDuty, Opsgenie, future incident/alerting tools) to be endpoint-routed: per-subscriber secrets encrypted on the channel endpoint resource, a stateless provider that resolves routing from channelData at send time,…