opengovsg

Repository-specific code smells and blessed conventions for the Isomer Next monorepo. Use when writing or reviewing code in this repo (tRPC routers, Kysely/Prisma access, zod schemas, React components, tests) to catch deviations from team conventions, and when the user wants to record a new code smell or best practice ("remember this convention", "add a code smell", "we always/never do X here").

Use this skill when the user asks to review, evaluate, or assess a dependency upgrade — e.g. "review this upgrade", "is bumping X from a.b.c to x.y.z safe?", "what breaks if I upgrade <pkg>?", "check this package bump". Covers pnpm/npm packages and github-actions. Researches breaking changes for every intermediate version and reports which ones actually impact the user's codebase. Also runs unattended on Dependabot PRs via GitHub Actions — no human in the loop.

Implement the minimal fix for an already-triaged bug, run the full test suite, and open a stacked PR via Graphite. Requires the `triage` skill to have run first.

Implement a feature ticket. Hard guardrails — Storybook (FE) or tRPC test (BE) required, area conventions enforced via CLAUDE.md, stacked PRs via Graphite. Picks up from `feature-plan` or one-shot when eligible.

Produce 2-3 implementation approaches with trade-offs for a scoped feature ticket. Stops and waits for a human to pick. Does not write code.

Grade a pull request against the project risk taxonomy, flag hot-path touches, surface missing tests/stories, and post a structured review comment. Does not approve or merge.

Triage a bug from a Linear ticket — reproduce, locate suspect code, write a failing test. Stops before fixing. Use as the first step of any bug-driven agent run.

This writes a pull request (PR) description for the current branch.

The FormSG Oracle — an internal assistant for the FormSG team at Open Government Products (Singapore). Use this skill whenever a FormSG team member asks *why* the product behaves a certain way, asks about past decisions, design rationale, architectural trade-offs, or historical context. Triggers include questions like "why do we do X", "when did we decide Y", "what was the reason for Z", "has this been discussed before", "what does the ADR say about", or any question implying institutional memory about FormSG. Always use this skill — not general knowledge — when answering FormSG product history questions, even if you think you already know the answer.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along four independent axes — Standards, Spec, Architecture, and Divergent design — each run as a parallel sub-agent so contexts stay clean, then verified against false positives and reported side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

Assemble a review-ready PR body and inline comments from the breadcrumbs the implementation loop captured, the ADRs in the touched area, and the originating PRD. Use when the user has finished implementation on a branch and wants to ship for review.

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, domain doc layout, and review-prep conventions (commit style and breadcrumb schema). Run before first use of `to-issues`, `to-prd`, `tdd`, `improve-codebase-architecture`, `zoom-out`, or `prepare-for-review` — or if those skills appear to be missing context.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

Test-driven development with red-green-refactor loop, including frontend slices verified against a Figma design source via Storybook stories and an agent-browser visual gate. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, asks for test-first development, or wants to implement a UI/component/page from a Figma design.

Cut a Plumber release PR that merges `develop-v2` into `production`. Prompts the user to choose the version bump (patch / minor / major), bumps the version across the root workspace and every package via `npm version`, creates a single conventional `vX.Y.Z` commit + git tag locally, and prepares (or opens) the release PR whose body summarises the changes since the last release. Use when the user asks to cut/prepare a release, make a release PR, bump the version and release, or ship develop-v2 to production.

Plan production monitoring (Datadog) for a feature that was just built or is being reviewed. First grills the author about likely failure modes, then inspects the codebase to find existing metrics/traces/logs to reuse, recommends the minimal instrumentation changes needed, and outputs a human-readable monitoring plan plus Datadog monitor definitions as JSON. Use after building/reviewing a backend or frontend feature, or when asked what to monitor or to set up Datadog monitors/alerts on traces, logs, or RUM.

Work with Graphite (gt) for stacked PRs - creating, navigating, and managing PR stacks.