Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From critic
Assess downstream effects of editing a chapter. Use when the user has edited a chapter and wants to know what breaks in later chapters.
How this skill is triggered — by the user, by Claude, or both
Slash command
/critic:downstreamThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The vault path for all tool calls is: ${user_config.vault_path}
The vault path for all tool calls is: ${user_config.vault_path}
Assess what breaks in later chapters after editing a chapter.
$ARGUMENTS should be a chapter name (e.g., "chapter-03").
Call the assess-downstream tool with the vault path (current working directory) and chapter name.
Present results as readable text:
Summary: The overall assessment.
Downstream Issues (grouped by severity): For each issue:
Safe Chapters: List chapters that appear unaffected.
After presenting, offer:
npx claudepluginhub jdpedrie/critic --plugin criticGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.