菜单
Run FMC pre-commit verification (bun run check, bun run format), fix failures, and draft commit messages. Use when finishing a task, wrapping up changes, preparing to commit, running checks/tests/lint/typecheck/e2e, or when the user asks to "finish work", "run checks", or "create a commit message".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
React 19 + TypeScript for FMC TanStack Start apps: typed components, events, generics, ref-as-prop, Compiler-first memoization, and useEffect discipline (naming, when not to use Effect, alternatives). Use when typing React components/hooks/events, or writing/reviewing useEffect, useEffectEvent, derived state, data-fetch effects, or eslint-plugin-react-hooks effect rules. Not for routing/server boundaries (see tanstack-start-* skills).
react-map-gl/maplibre patterns for FMC geo apps: declarative Source/Layer (never addSource/addLayer), MapProvider + useMap(), interactiveLayerIds, flat Source/Layer, map-loaded guard, Map event handlers (not useEffect), URL map state, initialViewState, cursor, feature state, missing images. Use when building or reviewing Map components, layers, click/hover handlers, setFeatureState, or map URL sync in TanStack Start / Vite apps. Reference implementation: tilda-geo/app.
Review and merge Dependabot PRs for FMC repos (tilda-geo, trassenscout, etc.): changelog triage, risk classification, CI verification, and rebase merge. Use when triaging dependency update PRs, weekly Bun/GitHub Actions/Docker bumps, grouped patch PRs, security updates, or semver-major upgrades.
Default FMC tech stack for geo-heavy React SPAs: Bun/Vite, React 19, TanStack, maps, styling, TypeScript editor/CLI alignment, tsconfig templates, browserslist client targets, and when to pick sibling skills. Use when scaffolding a new app, evaluating libraries, changing supported browsers or compat lint, or making stack/architecture decisions on existing apps.
FMC conventions for Zustand v5 in React: file naming, custom-hook-only exports, atomic selectors, actions namespace, small focused stores. Use when adding or reviewing client global state, or debugging unnecessary re-renders and SSR/persist hydration issues. Not for server/async data (TanStack Query) or URL state (nuqs). For API details, middleware, slices, and migration, use the official llms.txt index below.
| name | finish-work |
| description | Run FMC pre-commit verification (bun run check, bun run format), fix failures, and draft commit messages. Use when finishing a task, wrapping up changes, preparing to commit, running checks/tests/lint/typecheck/e2e, or when the user asks to "finish work", "run checks", or "create a commit message". |
Standard FMC workflow before committing. Run commands in the project root (or the package that owns the changed code in a monorepo).
- [ ] Step 1: bun run check
- [ ] Fix any failures; re-run until green
- [ ] Step 2: bun run format
- [ ] Re-run check if format changed files that affect lint/types/tests
- [ ] Draft commit message (see below)
- [ ] Commit only when the user explicitly asks
bun run checkRuns the project's aggregate verification script. In FMC apps this typically includes:
bun run type-check → tsc --noEmit; skill tech-stack)--deny-warnings)vitest run, test-run, etc.)format-check / check-format inside check)check is defined per repo in package.json — read it if unsure what runs.
E2E: If Playwright/e2e is not part of check but the repo has a e2e script and the change touches UI, routes, or auth flows, run bun run e2e before finishing. Skill playwright-skill for setup and patterns.
On failure: fix the root cause, then re-run bun run check. Do not skip failing steps.
bun run formatApplies oxfmt (or project formatter) with write mode. Fixes import/class sorting and style.
check so lint/type fixes are in place first.check already runs format in write mode, still run bun run format as the final pass — it catches anything check missed or that edits introduced mid-fix.Stage formatting-only changes together with the functional changes they belong to.
Draft when checks pass. Do not commit unless the user explicitly requests it.
<Topic>: <Desc>
Map, Auth, Processing, Deps, …). Match repo conventions when obvious from the diff.Bullet list of meaningful changes (behavior, not file names):
- Add viewport clamping for region bounds
- Fix stale loader cache after logout
- Update oxlint config for compat plugin
If the user mentioned a GitHub PR or issue in the conversation, add a Ping line in the body with the full URL:
Ping https://github.com/FixMyBerlin/tilda-geo/pull/1234
Use the exact URL from context (PR or issue). One Ping line per referenced item.
Region map: clamp initial viewport to bounds
- Derive max bounds from region GeoJSON before fitBounds
- Skip clamp when URL already has explicit zoom
Ping https://github.com/FixMyBerlin/tilda-geo/issues/5678
Run check / format in each package you changed (app/, processing/, etc.) when scripts live per package. Prefer the same order: check → format per package.
tech-stacktech-stack → oxc-config.mdplaywright-skillbabysit