// Run pnpm test from the repo root and fix failing tests or implementation until the suite passes. Use after edits, when CI is red on tests, or before opening a PR. Keywords: pnpm, test, vitest, unit tests, monorepo.
Run pnpm build from the repo root and fix compile or build errors until the workspace build passes. Use after edits, when CI is red on build, or before opening a PR. Keywords: pnpm, build, TypeScript, monorepo, workspace.
Run pnpm format then pnpm lint from the repo root and fix issues until both pass. Use after edits, when CI is red on lint/format, or before opening a PR. Keywords: pnpm, format, lint, trunk, monorepo, code style.
Manage Architecture Decision Records (ADRs). Use this to initialize, create, list, and link ADRs to document architectural evolution. Requires 'adr-tools' to be installed.
Use at the end of a coding session to summarize outcomes, failures, inefficiencies, and root causes, then output a concise postmortem report with ranked improvements for next time. Output only in chat; do not edit project files unless the user explicitly asks. Skip nit-picks and one-off mistakes.
Assign @copilot on an existing SecOps remediation issue after policy guard—use when Project link or org policy requires Issue → Project before assignee. Uses gh issue edit; does not push branch code.
One-shot PR status check with gh—structured JSON outcome and exit codes; classify green vs failing vs pending vs blocked. Read-only on the repo. Does not loop; re-invoke on a schedule (human, Claude, or optional sub-agent). No issue comments—use secops-post-ci-nudge-comment to nudge.
| name | test-fix |
| description | Run pnpm test from the repo root and fix failing tests or implementation until the suite passes. Use after edits, when CI is red on tests, or before opening a PR. Keywords: pnpm, test, vitest, unit tests, monorepo. |
pnpm test failed locally or in CI.Working directory: Repository root (directory that contains the root package.json).
Run:
pnpm test
Root test is vitest run per package.json. Vitest is configured at the repo root; tests are typically under packages/*/src/**/*.{test,spec}.ts — fix code or tests in the paths reported by failures.
On failure: Read command output. Fix incorrect expectations, broken implementations, or test setup. Then run pnpm test again.
Iteration cap: After 5 failed pnpm test runs, stop and summarize remaining failures; do not loop indefinitely.
Success: The last pnpm test exits with code 0.
There is no separate test:all script in package.json; use pnpm test as the single entry point for this repo’s Vitest setup.