Menu
Use when reviewing TypeScript changes for alignment with ts-coding-standards, Biome lint rules, and repository conventions before merge or handoff.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when implementation work in this repository changes behavior, adds functionality, or fixes bugs and the user has not explicitly asked to avoid workflows. Routes the work through the project-local divedra workflow `divedra-workflows/design-and-implement-review-loop`, including design/plan alignment, implementation, review, user-facing documentation refresh, and final handoff.
Use when creating or organizing design documents. Provides directory structure, file naming, and content guidelines for design specs and references.
Use when a divedra workflow, CLI command, GraphQL control plane, event listener, or submodule integration appears to fail because of an upstream divedra bug. Requires reproducing with the local submodule, filing an issue in tacogips/divedra when the bug is real, fixing the submodule, validating it, and committing the divedra change.
Use when helping an end user run, inspect, monitor, resume, continue, rerun, or troubleshoot existing divedra workflows. Applies to workflow list/status/validate/inspect/run, session progress/status/resume/continue/rerun, GraphQL inspection, mock scenarios, workflow roots, runtime artifacts, local serve, GraphQL endpoint execution, and event-triggered workflow usage.
Use when creating, modifying, reviewing, or validating divedra workflow bundles. Applies to step-addressed workflow.json authoring, node payload files, prompt files, built-in node add-ons, cross-workflow transitions, manager/worker routing, and portable workflows under a workflow root.
Use when testing or verifying divedra workflow bundles. Applies to deterministic mock-scenario runs, workflow validate/inspect/run checks, EXPECTED_RESULTS.md updates, regression assertions, session output verification, and CI-style workflow fixture validation.
| name | ts-review |
| description | Use when reviewing TypeScript changes for alignment with ts-coding-standards, Biome lint rules, and repository conventions before merge or handoff. |
| allowed-tools | Read, Grep, Glob |
Use this skill after substantive TypeScript edits (or before approving a PR) when you need a structured pass beyond automated checks.
.agents/skills/ts-coding-standards/SKILL.md and scan the linked topic files that apply to the change (error handling, types, layout, async, security).biome check . --diagnostic-level=warn (or bun run lint:biome), bun run typecheck, bun run test, and Prettier on touched paths where formatting applies.Confirm the implementation matches what the ts-coding agent requires:
no any, indexed access, optional/exactOptionalPropertyTypes), Result/error patterns where appropriate, and project layout conventions..agents/skills/ts-coding-standards/security.md.--diagnostic-level=warn (warnings are visible; infos are not). There must be no errors in that output for files under src/ and vitest.config.ts. Treat warnings as normal review/fix targets unless the team agrees to defer them. Do not recommend weakening rules to hide violations unless the user explicitly approves a config change.src/ should stay at or below 1000 lines (Biome enforces this). Test files may temporarily exceed that; still flag unreasonably large *.test.ts files as follow-up work..agents/skills/ts-coding-standards/project-layout.md.Summarize Pass or Issues with bullet points referencing file paths and concrete fixes. If Biome or tsc failures exist, quote the diagnostic and suggest the minimal correction.