finish-work

name	finish-work
description	FMC finish-work workflow: run bun run check, fix failures, draft user-facing English commit messages, and actually commit when user indicates commit intent ("and commit", "commit it", "land this"). Use for finish work, run checks, wrap up, prepare commit messages, or create commits.

Finish work

Run in the project root, or in each changed monorepo package (app/, processing/, etc.).

Workflow

1. Verify: read scripts.check in package.json, run bun run check, fix the root cause, and rerun until green. lint/format may rewrite files.
2. Keep fixes together: stage lint/format changes with the functional changes; never make a separate "lint" or "format" commit.
3. Draft the commit message using the format below.
4. Decide from user intent:
   • Commit intent present: actually run git commit; do not stop at a draft.
   • No commit intent: show the drafted message only.

Commit intent includes: "and commit", "then commit", "commit it", "land this", "create a commit", or "finish work" plus a commit phrase in the same or earlier user turn.

Commit path: git status, git diff, and git log -5 in parallel; stage relevant files only; git commit via HEREDOC; git status to verify.

Safety: no push unless asked. No --no-verify. No amend of pushed commits. Do not stage secrets or unrelated dirty files.

Already committed and check only fixed lint/format: git commit --amend --no-edit when the user wants commit/amend and HEAD has not been pushed; otherwise stage and ask.

E2E is not in check. For UI/routes/auth changes, also run bun run e2e (or check-full on trassenscout). See playwright-skill.

Commit message

<Topic>: <Desc>

- <user-facing outcome bullet>
Ping https://github.com/org/repo/pull/123

• Topic: scope (Map, Auth, Processing, Dev, etc.). FMC internal-only changes (deps, CI, tooling) use Dev.
• Desc: imperative outcome, not filenames.
• Body: bullets of what users/operators see, do, or get after this lands. Include why when the conversation established it. Stay at outcome level; do not list files, symbols, refactors, or diff steps. Bodies feed user-changelog, so they must be readable without the patch.
• Ping: if user cited a PR/issue, add one Ping <full-url> line per item.

Example:

Region map: clamp initial viewport to bounds

- Users: map fits selected region on load instead of generic Germany view (confusing deep links)
- Preserve explicit zoom in URL so shared links do not jump
Ping https://github.com/FixMyBerlin/tilda-geo/issues/5678

Internal-only (no user-visible change): maintainer bullets ok; omit user bullets when none apply.

Related

playwright-skill | tech-stack | review-dependabot / babysit | user-changelog