Explorar comunidad

Run failing tests repeatedly, classify each failure as flaky or real, and fix only confirmed regressions.

When implementation claims done, a separate verifier pass runs build, lint, and tests with no access to the implementer's rationale.

Run the production build, fix compile and bundling errors, and loop until the build succeeds.

On an interval, hit health and smoke endpoints after a deploy until all checks return healthy responses.

Run end-to-end tests, fix UI and integration failures, and loop until the E2E suite passes.

Run Playwright or Percy visual snapshots on UI changes; fix unintended diffs until baselines match intentionally.

Add focused tests until coverage meets your threshold (e.g. 80%), without changing production behavior unnecessarily.

Upgrade a single outdated package per iteration, fix breakages, and commit — safer than bulk npm update.

Every 15 minutes, inspect open PRs with a watch label: nudge reviewers, fix CI, rebase if behind main.

Test-first loop: write a failing test, implement the minimum code to pass, refactor, and repeat.

Run lint and typecheck, fix reported issues, and loop until the codebase is clean.

Run your test suite, fix the smallest root cause on failure, and repeat until every test passes.

Fresh-context loop: pick one incomplete story from prd.json, implement it, run backpressure checks, commit, and update progress before the next iteration.

Poll CI on an interval, investigate failures when checks go red, and push fixes until green.

Loop until API responses match the OpenAPI or JSON Schema contract — catch drift between docs and implementation.

Implement on a branch, run tests, push, open a PR, wait for CI, and loop until checks pass and the PR is ready to merge.

Hook that runs tests before git commit commands to block commits when the suite is red.

Keep openapi.yaml valid and in sync with route handlers — lint the spec and fix drift each pass.

Review your own diff like a senior reviewer, fix issues, and repeat for three passes before opening the PR.

Ship features without bloating the client bundle — loop until size checks pass under your budget threshold.

On each failed repro attempt, write a short reflection to disk, then retry with that memory — avoids repeating the same wrong fix.

Fetch the latest failed CI run, reproduce the failure locally, fix it, and repeat until checks pass.

Run a fixed smoke checklist against staging after deploy: auth, core flows, and error budgets.

Run database migrations, fix schema issues, and loop until migrations apply cleanly in dev.