commit
- Repo stars 1,537
- Author repo cafe-hass
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @FezVrasta · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
Run all checks in parallel:
If any check fails: Lint errors: Run `yarn lint:biome --fix` to auto-fix, then manually fix remaining issues Type errors: Fix TypeScript errors in the affected files Formatting: Run `yarn format` (i.e. `yarn format:check --fix`) to auto-format all files Re-run the failing checks after fixing until they all pass. Do NOT proceed to commit until every check passes with zero errors.
Only after all checks pass, follow the standard commit process: Run `git status` and `git diff` to review changes Stage the relevant files with `git add <specific files>` Write a clear commit message following the existing style Create the commit using a heredoc for the message:
The user wants to commit changes. Before creating any git commit, you MUST run all quality checks and fix any issues found. Follow these steps in order:
## Step 1: Run quality checks
Run all checks in parallel:
```bash
yarn lint:biome --fix
yarn typecheck
yarn format:check --fix
yarn test
```
## Step 2: Fix all issues
If any check fails:
- **Lint errors**: Run `yarn lint:biome --fix` to auto-fix, then manually fix remaining issues
- **Type errors**: Fix TypeScript errors in the affected files
- **Formatting**: Run `yarn format` (i.e. `yarn format:check --fix`) to auto-format all files
Re-run the failing checks after fixing until they all pass. Do NOT proceed to commit until every check passes with zero errors.
## Step 3: Create the commit
Only after all checks pass, follow the standard commit process:
1. Run `git status` and `git diff` to review changes
2. Stage the relevant files with `git add <specific files>`
3. Write a clear commit message following the existing style
4. Create the commit using a heredoc for the message:
```bash
git commit -m "$(cat <<'EOF'
<message here>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
EOF
)"
```
5. Run `git status` to confirm the commit succeeded.
**IMPORTANT**: Never use `--no-verify` or skip hooks. Never commit if any lint, typecheck, or format check is failing.
Listed in source order.
sections -> Step 1: Run quality checks → Step 2: Fix all issues → Step 3: Create the commit
terms -> Lint errors · Type errors · Formatting · IMPORTANT
files/cmd -> yarn lint:biome --fix · yarn format · yarn format:check --fix · git status · git diff · git add <specific files> · --no-verify
body sha256 -> 622159f8e9b5
Step 1: Run quality checks
Run all checks in parallel:
Step 2: Fix all issues
If any check fails: Lint errors: Run
yarn lint:biome --fixto auto-fix, then manually fix remaining issues Type errors: Fix TypeScript errors in the affected files Formatting: Runyarn format(i.e.yarn format:check --fix) to auto-format all files Re-run the failing checks after fixing until they all pass. Do NOT proceed to commit until every check passes with zero errors.Step 3: Create the commit
Only after all checks pass, follow the standard commit process: Run
git statusandgit diffto review changes Stage the relevant files withgit add <specific files>Write a clear commit message following the existing style Create the commit using a heredoc for the message: