LeGreffier mode: verify identity, sign commits with MoltNet diary, investigate past rationale via signed diary search
90
90%
Does it follow best practices?
Impact
90%
2.64xAverage score across 5 eval scenarios
Advisory
Suggest reviewing before use
A team building a task-extraction pipeline harvests benchmark tasks from git commit history. The pipeline groups related commits into logical tasks and uses specific markers to identify complete, verified task chains. However, the quality of extraction depends heavily on how developers shape their commits — mixed, sprawling commits produce unusable tasks.
The team needs a planning tool that takes a description of upcoming work and produces a commit plan: how to split the work into well-shaped commits, what metadata to attach, and what checks to run before pushing. The tool should also understand when work can be declared "complete" vs when it still needs verification.
Create the following files:
commit-planner.ts — A TypeScript module that exports:
planCommitChain(workDescription: string, filesToChange: string[]): CommitPlan functionCommitPlan type with individual commit descriptions, ordering, and metadatagenerateCommitMessage(commit: PlannedCommit): string functionverificationRequired(changeType: string): string function that returns what evidence is needed before work can be marked donepre-push-checklist.ts — A TypeScript module that exports:
PrePushCheck type and runPrePushChecklist(repoState: RepoState): CheckResult[] function that validates the repository is ready to pushsplitting-guide.md — A document explaining the commit splitting philosophy, practical heuristics, and when changes should be considered verified vs merely written.
The following files are provided as inputs. Extract them before beginning.
=============== FILE: inputs/work-description.txt =============== Task: Add rate limiting to the REST API
Changes needed: