oat-project-reconcile

You can sync manual commits with project task tracking by analyzing Git history and updating OAT tracking artifacts. This tool maps commits to planned tasks using commit messages, file overlap, and temporal ordering, requiring human confirmation for uncertain assignments to keep project state accurate.

Commit mapping works by analyzing Git history signals including commit messages, file overlap, and temporal ordering to match unrecorded commits to tasks defined in plan.md. It then updates implementation.md and state.md to reflect the reconciled work accurately.

Yes, you need OAT CLI, Git, and access to project artifacts like plan.md, implementation.md, and state.md. These dependencies are required to analyze commit history and accurately update the OAT tracking files during reconciliation.

Yes, the reconciliation process uses a human-in-the-loop confirmation mechanism. It requires your explicit approval for uncertain commit-to-task mappings and task status changes before updating the final project tracking artifacts.

The best way to track manual code changes outside the OAT workflow is using a reconciliation script that bridges manual commits with planned tasks. It automatically suggests task fulfillment and updates tracking files like implementation.md accordingly.

If commit analysis cannot confidently map a commit to a task, the Skill flags the uncertain assignment and prompts for human confirmation. This ensures no manual code changes are incorrectly attributed to planned project tasks.