sync-and-commitlisted

Verify the work is consistent, complete, and accurate; sync the docs tree; commit and push. Use at the end of a TDD phase or step (especially when called from ship-milestone), or whenever the operator wants to wrap up in-flight work. Reads CLAUDE.md for project conventions; runs `docs check` against the docs tree; never bypasses git hooks; never pushes to `main`.
ArtRichards/sync-and-commit · ★ 0 · Code & Development · score 70

Install: claude install-skill ArtRichards/sync-and-commit

# sync-and-commit End-of-step wrap-up. Verify the work, sync the docs tree to reality, and commit (and push, when on a feature branch with a remote). Optionally pairs with [`docs-cli`](https://github.com/ArtRichards/docs-cli) **v1.2.0 (M7+)** for the `Lifecycle:` / `Role:` / `Updated:` metadata convention used by `project-foundation`, `create-milestones`, and `ship-milestone`. If the project does not use docs-cli, the docs-side checks are skipped and only the project's own verification commands run. ## Step 1 — Read project context Read `CLAUDE.md` at the repo root for: - The docs-tree location (if any) and which artifacts live in it. - Build/test/quality commands. - Commit message conventions. - Branch conventions (especially: which branches are safe to push to vs. which require operator review). - Any project-specific rules. If CLAUDE.md is missing, fall back to inspecting recent `git log --oneline` for commit style and `package.json` / `pyproject.toml` / `Makefile` for commands. ## Step 2 — Technical verification Quick sanity pass: read through the diff. Anything obviously wrong or incomplete? Then walk the checklist. ### 2a. Code completeness For the phase/step just completed, verify: - All required functionality is implemented (check against the milestone spec). - No placeholder code, `TODO`/`FIXME` comments, or "implement later" stubs left behind. - No commented-out code that should be removed. - All edge cases from the spec are handled. - Error handlin