Generates a structured crit story JSON from git diffs using the crit CLI.
npx skills add https://github.com/tomasz-tomczyk/crit --skill crit-story
Please help me install this Agent Skill. Skill: crit-story Source: https://github.com/tomasz-tomczyk/crit/tree/main/integrations/claude-code/skills/crit-story Command: npx skills add https://github.com/tomasz-tomczyk/crit --skill crit-story
Turning a raw git diff into a coherent, human-reviewable narrative is tedious: hunks must be clustered by theme, coverage must be complete, and the output must match a strict schema. This Skill automates authoring a crit story from the current diff so reviewers get an organized walkthrough instead of a flat patch.
crit story --guide, ensuring the output follows the user's customized rules.crit story --prep so no change is omitted.crit story --story-file, receiving coverage reports on missing or duplicated hunks and drift detection when the diff changes.Ask your agent to generate a crit story for the current branch changes using the crit-story skill.
High-intent search queries and answers about installing and using this skill.
Invoke the crit-story skill explicitly or run the crit story commands directly. The workflow fetches the authoring guide with crit story --guide, writes the full diff with crit story --prep, authors the JSON, then ingests it with crit story --story-file.
Use crit-story only when you explicitly want a story generated from a diff; it is a sibling skill that does not run inside the normal /crit review loop. It should not be inferred from generic review, PR, or diff-review requests.
The JSON must contain only prologue, chapters, and support. Fields like version, generated_at, agent, base_sha, head_sha, scope_fingerprint, and coverage are filled in automatically by crit and must be omitted.
Rejection happens when hunks are duplicated across chapters or when the diff changed since prep, causing a drift error. The coverage report is printed as JSON on every attempt; fix duplicates or re-run crit story --prep and re-author from the fresh prep file.
If missing hunks are detected with auto_repaired set to true, crit back-fills the omissions into the support array and still exits successfully. You can optionally re-author the story to place those hunks deliberately.
furiosa-aiAnalyze the final diff to propose atomic commits for a clean PR history.
AradotsoOrganize local git diffs into logical chapters for code review.
tomasz-tomczykManage Crit CLI review files and comments programmatically.
superplanehqWrite Git commit messages and pull request descriptions using Conventional Commits and Simplified Technical English.