check-and-commit
GitHub执行预提交验证门控,依次运行类型生成、Biome检查、类型检查和测试等。自动修复简单失败,填充缺失的国际化字符串,并在所有检查通过后提交代码。
Trigger Scenarios
Install
npx skills add crbnos/carbon --skill check-and-commit -g -y
SKILL.md
Frontmatter
{
"name": "check-and-commit",
"description": "Pre-commit verification gate — runs Carbon's validation gates in order (generate:types if schema changed, biome, scoped typecheck, scoped tests, build if needed, and \/translate to fill missing i18n .po strings when UI\/locale files changed), fixes straightforward failures, then commits the specific files with a conventional message. Use after \/fix, after an \/execute task, or after manual changes when the work should be committed. Commits only when every gate is green; pushes only if the branch already tracks a remote or the user asked."
}
check-and-commit — verification gate, then commit
Run the gates in order, fix what's mechanically fixable, and commit only when everything is green. This skill is the only place in the workflow that commits.
Announce at start: "Using the check-and-commit skill — running the gates, then committing."
Step 1: Identify what changed
git status --porcelain
git diff --name-only HEAD # staged + unstaged vs HEAD — the full change set
Derive every flag below from git diff --name-only HEAD (all changes vs the last
commit). Plain git diff --name-only omits already-staged files, which would let
staged UI/.po files slip past I18N_RELEVANT and skip Gate 6. From the changed
paths, derive:
-
SCHEMA_CHANGED— any file underpackages/database/supabase/migrations/ -
WORKFLOW_CATALOG_RELEVANT— the diff touchesSCHEMA_CHANGEDpaths,packages/database/src/swagger-docs-schema.ts, or the workflow catalog source (packages/workflows/src/catalog/**, e.g.entities.ts,actions.ts,moments.ts,operations.ts,labels.ts). The catalog is generated from the DB schema plus that source, so a new column or entity change silently staleness the committed*.generated.ts. When true, Gate 1c regenerates the catalog so the generated copy ships in this same commit. This gate fails regularly and is easy to miss — a schema change that adds a column the workflow engine surfaces breakscheck:workflow-catalogeven though nothing underpackages/workflowswas edited by hand. -
I18N_RELEVANT— the diff adds/edits UI source that can introduce new translatable strings (apps/erp/app/**,apps/mes/app/**,packages/react/src/**) or touches anypackages/locale/locales/**/*.po. When true, Gate 3 (i18n) fills missing translations so they ship in this same commit instead of drifting behind the code. -
the set of touched packages — run this to map changed files to workspace package names (these are the
--filtervalues for the gates):git diff --name-only HEAD | while read -r f; do d=$(dirname "$f") while [ "$d" != "." ] && [ ! -f "$d/package.json" ]; do d=$(dirname "$d"); done [ -f "$d/package.json" ] && sed -n 's/.*"name": *"\([^"]*\)".*/\1/p' "$d/package.json" | head -1 done | sort -u -
whether any file is outside the intended change (leftover debug file, unrelated edit). If yes → exclude it from staging and mention it in the report.
Step 2: Run the gates in order
Stop on failure, apply the fix policy (Step 3), re-run the failed gate.
# Gate 1 — types (only if SCHEMA_CHANGED)
pnpm run generate:types
# then include the regenerated files in the commit
# Gate 1c — workflow catalog (only if WORKFLOW_CATALOG_RELEVANT)
pnpm run generate:workflow-catalog # regenerate from schema + catalog source
pnpm run check:workflow-catalog # must exit 0
# then include the regenerated packages/workflows/src/catalog/*.generated.ts in the commit.
# If check:workflow-catalog still fails after regenerating (e.g. a declared moment
# with no raise site, or a raise site naming an undeclared moment) it is a real
# code problem, not staleness — fix the source per its message, don't commit around it.
# Gate 2 — format + lint (auto-fixes in place)
pnpm exec biome check --write --no-errors-on-unmatched <changed paths>
# Gate 3 — typecheck, one package at a time. NEVER whole-repo (`pnpm typecheck`
# runs every package at once and OOMs the machine).
pnpm exec turbo run typecheck --filter=<pkg> # repeat per touched package
# Gate 4 — tests per touched package
pnpm --filter <pkg> test
# Gate 5 — build, ONLY if the change affects build outputs
# (package exports, config files, SST infra)
pnpm exec turbo run build --filter=<pkg>
Gate 6 — i18n translations (only if I18N_RELEVANT)
Run last, after the code gates are green — so no Haiku translation effort is
spent on a commit that would fail typecheck/tests. Fill missing .po
translations by invoking the translate skill (/translate), not by hand:
- Invoke
/translate. It refreshes catalogs (lingui:extract), fans missingmsgstrout to Haiku subagents, merges deterministically, and verifies withlinguito check— see.claude/skills/translate/SKILL.mdfor the full loop. - If it reports
NOTHING_TO_TRANSLATE/linguito checkalready clean → nothing to add; mark the gate SKIP and continue. - Otherwise it fills
packages/locale/locales/**/*.po. Treat the gate as PASS only when/translatefinishes withRemaining ... : 0andlinguito checkexits 0. If it stops with a residual after its 3-round cap → STOP, report BLOCKED (don't commit half-translated catalogs). - The filled
.pofiles are now part of this change — add them explicitly in Step 4 alongside the code (their package is@carbon/locale)./translateremoves its own.ai/scratch/translate/scratch; never stage that.
Step 3: Fix policy
| Failure | Action |
|---|---|
| Biome formatting/import order | Already fixed by --write; re-run to confirm clean |
| Type error from stale generated types | Run Gate 1, re-run typecheck |
| Type/test error caused by this change | Fix the code, re-run |
| Pre-existing failure, unrelated to this change | Note in report; don't block, don't fix |
| Anything unclear or still failing after 2 fix attempts | STOP — report BLOCKED |
"Pre-existing" must be proven, not assumed: the failing file/test is untouched by this diff, or the same failure reproduces on the merge-base. If you can't show one of those, treat it as caused by this change.
Red flags — thinking any of these means the gate is being weakened; STOP:
- "I'll run the gates once at the end instead of in order"
- "
git add -Ais faster" - "that failure is probably pre-existing" (prove it — see above)
- "the gate is flaky, I'll just retry until it passes"
Step 4: Commit
Only when all applicable gates pass:
git add <each changed file, listed explicitly> # NEVER `git add -A` or `git add .`
git commit -m "<type>(<scope>): <description>"
- Types:
fix,feat,chore,refactor,test,docs. Scope = module or package (fix(inventory): …). - Staging is explicit because worktrees accumulate runtime files (env files,
screenshots,
.jsonldebug logs) that must never be committed. - Push only if the branch already tracks a remote (
git rev-parse --abbrev-ref @{upstream}succeeds) or the user asked to push. Otherwise leave the commit local and say so.
Step 5: Report
## Check & Commit Report
**Result:** COMMITTED | BLOCKED
| Gate | Result | Notes |
|------|--------|-------|
| generate:types | PASS / SKIP | |
| workflow-catalog | PASS / SKIP | <regenerated + check exit 0> |
| biome | PASS | <files auto-fixed> |
| typecheck (<pkgs>) | PASS | |
| test (<pkgs>) | PASS | <pre-existing failures noted> |
| build | PASS / SKIP | |
| i18n (/translate) | PASS / SKIP | <N filled across locales, or "no missing"> |
**Commit:** `<sha>` — `<message>` · **Pushed:** yes/no
**Excluded from staging:** <files left uncommitted and why, or "none">
If BLOCKED: name the gate, the concise error, and what was attempted.
Version History
-
f9d7efd
Current 2026-10-20 03:32
重构:将文档内容移至@carbon/content包,移除旧的agent知识库生成步骤,集成zbsearch引擎提升搜索能力。
- a82ca72 2026-09-23 07:30
- dd8f587 2026-08-20 16:17


