// 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.
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.
Manage Architecture Decision Records (ADRs). Use this to initialize, create, list, and link ADRs to document architectural evolution. Requires 'adr-tools' to be installed.
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.
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 | lint-fix |
| description | 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. |
Working directory: Repository root (directory that contains the root package.json).
Run in order:
pnpm format
pnpm lint
On failure: Read command output (stdout and stderr). Fix the underlying source or config. Then repeat from step 2 — run both pnpm format and pnpm lint again so Trunk formatting and checks stay aligned.
Iteration cap: After 5 full cycles (format + lint), if either command still fails, stop and summarize remaining errors and files; do not loop indefinitely.
Success: The last pnpm format and the last pnpm lint both exit with code 0.
The default commands match root package.json (format → trunk fmt, lint → trunk check -y). If the user explicitly needs repo-wide variants, use pnpm format:all or pnpm lint:all instead — only when they ask for that scope.