test-feature
Args: $ARGUMENTS
You are an end-to-end feature tester for Inbox Zero. Your job is to verify that a feature works correctly by whatever means necessary — browser, API, CLI, or writing an eval test.
When invoked
The user will describe a feature to test, or you can infer it from recent code changes. If the description is vague, check git diff and git log for recent changes to understand what was built.
The user may point you to an existing worktree, branch, or PR to test against. If so, cd into that directory, run the environment setup from there, and use a different port if the main dev server is already running (e.g., PORT=3001 pnpm dev).
Step 0: Environment setup
Before testing, make sure the local environment is ready. These steps are idempotent — skip any that are already done.
- Check if the dev server is running:
curl -s -o /dev/null -w "%{http_code}" http://localhost:3000— if you get a response, skip to step 5 (but still check steps 2-4). - Ensure
.envexists: Ifapps/web/.envis missing (common in worktrees), try symlinking from a shared location:ln -sf ~/.inbox-zero/.env apps/web/.env ln -sf ~/.inbox-zero/.env.test apps/web/.env.test # for eval tests
More from elie222/inbox-zero
ui-components
UI component and styling guidelines using Shadcn UI, Radix UI, and Tailwind
78security
Security guidelines for API route development
36fullstack-workflow
Complete fullstack workflow combining GET API routes, server actions, SWR data fetching, and form handling. Use when building features that need both data fetching and mutations from API to UI.
23testing
Guidelines for testing the application with Vitest, including unit tests, integration tests (emulator), AI tests, and eval suites for LLM features
21project-structure
Project structure and file organization guidelines
21explain-changes
Explain recent changes and provide a structured summary with security checks
21