agentsclimarketplace

Workflow fix and ship

Skill kensaurus/cursor-kenji/skills/workflow-fix-and-ship

🦖Curated Cursor AI agent skills, slash commands, MCP configs, subagents & rules for full-stack dev — React 19, Next.js 15, Supabase, Tailwind v4, TypeScript

Install
npx -y skills add kensaurus/cursor-kenji --skill workflow-fix-and-ship

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Complete bug-fix lifecycle in one sweep: triage production signals (Sentry / logs) → reproduce → fix (debug-error) → verify full-stack (test-playwright) → PR (workflow-pr) → post-deploy smoke (deploy-verify). Use when "fix this bug and close the ticket", "patch this and ship", "fix this Sentry issue", "bug report from user", or when a production error needs to go from alert to resolved in a single session.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, as published. Nobody here has run it

workflow-fix-and-ship — Bug Fix Lifecycle

Triage → fix → verify → ship. Every step leaves evidence.

Phase sequence

1. TRIAGE     → pull Sentry + logs, reproduce locally
2. ROOT CAUSE → debug-error (isolate, identify, understand)
3. FIX        → surgical change, matching tests
4. VERIFY     → test-playwright (confirm fix, catch regressions)
5. PR         → workflow-pr
6. POST-SHIP  → deploy-verify (optional if deploy is immediate)

Phase 1: Triage

Pull signals before touching code:

sentry:search_issues
{
  "organizationSlug": "<ORG>",
  "query": "<describe the bug>",
  "projectSlugOrId": "<PROJECT>",
  "regionUrl": "<REGION_URL>",
  "limit": 5
}

Then pull Supabase logs if the bug may be data-related:

supabase:get_logs
{
  "project_id": "<PROJECT_ID>",
  "service": "api"
}

Reproduce locally before any code change. State the exact repro steps.

Phase 2: Root cause (read debug-error)

Read the debug-error skill and follow it.

Required output: one-sentence root cause statement — "The bug is X because Y."

Phase 3: Fix

Rules:

  • Surgical change only — do not refactor unrelated code
  • Add a regression test that would have caught this bug
  • If the fix requires a schema change, apply via Supabase MCP and write the migration file

Phase 4: Verify (read test-playwright)

Read the test-playwright skill and follow it.

Drive the live app through the exact repro scenario. Confirm the fix resolves it. Check that nearby flows still work (regression scope = files touched ± 1 level).

Phase 5: PR (read workflow-pr)

Read the workflow-pr skill and follow it.

PR description must include:

  • Root cause (one sentence)
  • Sentry issue link or repro steps
  • Screenshot/recording showing the fix working

Phase 6: Post-deploy smoke (optional — read deploy-verify)

If deploying immediately after merge, read the deploy-verify skill.

Resolve the Sentry issue after confirming the fix is live in production.

Done criteria

  • Reproduced locally with exact steps
  • Root cause identified (not just "it was broken")
  • Regression test added
  • Smoke test confirms fix and no new breakage
  • PR open with root cause + evidence
  • Sentry issue resolved (after deploy confirmation)

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.