find-commit

To find git commits with generation metadata, you can filter repository history by keyword, file path, date range, or commit hash. The tool parses commit bodies for JSON metadata blocks and returns the associated plan, model, and unplanned changes for provenance tracing.

Generation-metadata in git commits is a JSON block containing the plan, model, plan file, and unplanned changes associated with a code generation session. It helps audit code changes by providing traceability, linking repository modifications directly back to their originating intent and reasoning.

To retrieve the plan and model details from an instrumented git commit, you query the repository history using a commit hash or date filter. The tool reads the commit body, parses the embedded JSON metadata, and outputs a structured array containing the plan contents and model information.

Yes, you can filter instrumented commits by file path and date range to locate specific code changes. The tool supports constraining search results using keywords, specific file paths, date ranges, and commit hashes to surface only the relevant generation metadata and touched files.

The best way to search git history for unplanned changes is to query for instrumented commits containing generation metadata. The tool parses these commits and explicitly returns the unplanned changes field, allowing you to identify deviations from the original plan during the generation session.

Find-commit works with standard git repositories but requires special instrumentation to be effective. It is designed to locate commits that include generation-metadata blocks produced by a compatible commit skill, meaning commits without these embedded JSON metadata blocks will not return provenance data.