菜单
The project's contribution mechanics — formatting, linting, type-checking, testing, the source-policy gate, the opt-in pre-commit hook, and how to commit. Use when setting up the repo, before committing, or when asked how to run checks/tests here.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Implement a new feature in this Deno Fresh app the project's way — typed fixture → KV accessor + SEED_VERSION bump → server-rendered route/component → bilingual + sourced → deno task check. Use when building a new page, data type, or visual on the dashboard.
Review a change against this project's blocking gates and quality bar — government sources, SEED_VERSION bump, deno check, translation provenance (machine-draft flags), KPI defensibility. Use before opening a PR or when asked to review the current diff or a PR for this repo.
Add a new KPI to data/kpis.ts with every defensibility field the README requires (definition EN+ML, source, owner, refresh, target, comparators, direction, civic domain, owner dept). Use when adding any headline or tier-2 KPI.
Orient quickly in this Deno Fresh 2 codebase — routing, the State/lang middleware, the Deno KV + typed-fixture data layer, islands, and where each kind of thing lives. Use before implementing a feature or when asked how the app is structured.
Scan data/ fixtures for English-without-Malayalam parity gaps (titleMl, definitionMl, nameMl, summaryMl). Use when reviewing data changes, before PR, or when asked about bilingual coverage.
Find and vet a government source before adding any number to the dashboard. Use when sourcing a new KPI, comparator, Government Order, or Status-Paper figure — turns "I need a number" into "I have an official, linkable source".
| name | contributing |
| description | The project's contribution mechanics — formatting, linting, type-checking, testing, the source-policy gate, the opt-in pre-commit hook, and how to commit. Use when setting up the repo, before committing, or when asked how to run checks/tests here. |
Mechanics for contributing to kerala-gov-mission-control. Full prose is in
CONTRIBUTING.md.
deno task dev # dev server at http://localhost:8000 (hot reload)
deno task check # deno fmt --check + deno lint + deno check ← run before every commit
deno task check:sources # government-source policy on data fixtures
deno task build # production build → _fresh/
deno task seed # wipe + reseed local KV from fixtures
deno task translate:test # pytest for scripts/translate.py
deno task review # advisory headless Claude review of staged changes
deno fmt (no --check) auto-formats. The PostToolUse hook already runs
deno fmt + deno lint on each edited .ts/.tsx.
deno task check is green (formatting, lint, types).deno task check:sources is green (every figure government-sourced).SEED_VERSION bumped if any data/*.ts fixture changed.dataStatus: "tbd") — /bilingual-audit.docs/specs/ for non-trivial features.A version-controlled hook lives in .githooks/. Enable it once per clone:
git config core.hooksPath .githooks
It blocks on deno task check + deno task check:sources and runs an
advisory (non-blocking) headless Claude review. Bypass a single commit with
git commit --no-verify; skip just the review with SKIP_REVIEW=1 git commit.
deno check) is the primary safety net — it's part of
deno task check.scripts/translate.py): deno task translate:test (pytest via uv).deno task dev + a screenshot for any visual change.Branch off main; never commit straight to main. Conventional-style messages
(feat:, fix:, chore:, docs:). CI (.github/workflows/ci.yml) runs
check + build on every PR — keep it green.