sheshbabu

Generate a concise commit message for the current staged or unstaged changes, written in the user's own style learned from git history. Use when the user asks for a commit message, or invokes /commit-message.

Generate a manual regression test checklist for the current changes, written from the user's point of view so they can click through the app themselves. Use when the user asks for manual test cases, a test plan, or invokes /manual-test.

Generate a concise commit message for the current staged or unstaged changes, written in the user's own style learned from git history. Use when the user asks for a commit message, or invokes /commit-message.

Generate a manual regression test checklist for the current changes, written from the user's point of view so they can click through the app themselves. Use when the user asks for manual test cases, a test plan, or invokes /manual-test.

Diagnose and fix the failing or flaky tests from the last stress run in stress.log. Use when the user runs `make heal`, invokes /heal, or asks to heal the suite.

Judge the screenshot diffs from the last visual run and say whether each change is intended, a regression, or noise. Use when the user runs `make visual`, invokes /visual, or asks to review visual diffs.

Diagnose and fix the failing or flaky tests from the last stress run in stress.log. Use when the user runs `make heal`, invokes /heal, or asks to heal the suite.

Judge the screenshot diffs from the last visual run and say whether each change is intended, a regression, or noise. Use when the user runs `make visual`, invokes /visual, or asks to review visual diffs.