promptpit

Review code

Run the project linter

Review code changes

Headless browser

Run the linter

Base level skill

Mid level skill

Top level skill

Generate React components

Headless browser for QA

Update CHANGELOG.md with user-facing changes. Use when the user wants to update the changelog, prepare for a release, or document what changed since the last version.

Write clear commit messages in conventional commits format. Use when the user is done with changes and wants to commit, says 'commit this', asks for a commit message, or has staged changes ready to go.

Systematic debugging - reproduce, isolate, understand, fix. Use when the user reports a bug, error, crash, unexpected behavior, or says something 'doesn't work' or 'is broken'.

Write useful documentation where people will find it. Use when the user asks to document code, add comments, update the README, explain a module, or write API docs.

Clean up code without changing behavior. Use when the user says code is messy, hard to read, too complex, wants to simplify, reduce duplication, or prepare code for a new feature.

Self-review code before pushing. Use when the user wants to check their changes, asks 'anything I missed', says 'ready to push', or wants a pre-PR sanity check.

Write tests for new or changed code. Use when the user asks for tests, says 'cover this', 'make sure this works', wants regression tests, or has just finished implementing a feature or fix.

Headless browser for QA testing