imbue

Quickly understand recent changes and extract actionable insights

Start a structured review workflow with evidence logging and formatted output

Autonomous agent for conducting structured reviews with evidence gathering. Use when detailed code reviews requiring evidence trails, architecture assessments with structured outputs, security audits with reproducible findings. Do not use when quick code check without formal review - use pensive skills. just catching up on changes - use catchup skill.

Use this skill to quickly understand "what changed and what matters". Use when resuming work after absence, preparing handoff documentation, reviewing sprint progress, analyzing git history for context. Do not use when doing detailed diff analysis - use diff-analysis instead. DO NOT use when: full code review needed - use review-core instead.

Use this skill for systematic change analysis with risk scoring. Use when analyzing specific changesets, assessing risk of changes, preparing release notes, categorizing changes by type and impact. Do not use when quick context catchup - use catchup instead. DO NOT use when: full PR review - use review-core with pensive skills.

Feature review and prioritization with RICE/WSJF/Kano scoring. Creates GitHub issues for suggestions. feature review, prioritization, RICE, WSJF, roadmap, backlog Use when: reviewing features or suggesting new features DO NOT use when: evaluating single feature scope - use scope-guard.

Enforces "prove before claim" discipline - validation, testing, and evidence requirements before declaring work complete. Use when claiming work is complete, recommending solutions, or finishing implementations, improvement validated, workflow optimized, performance improved, or issue resolved. Do not use when asking questions or for work clearly in-progress. MANDATORY: This skill is required before any completion claim.

Use this skill at the BEGINNING of any detailed review for consistent structure. Use when starting any detailed review workflow, needing consistent structure for capturing context and findings, ensuring comparable review outputs. Do not use when quick catchup without formal review - use catchup. DO NOT use when: diff-focused analysis - use diff-analysis.

Prevents sycophantic reasoning through checklist-based analysis, categorical integrity, and evidence-following to uncomfortable conclusions. Red Flags: "I agree that", "You are right", "Great point", "Absolutely", "That is a fair point", "I can see why", agreement without validation, softening conclusions, hedging without evidence, retracting under pressure. Use when analyzing conflicts, evaluating ethical claims, or noticing sycophantic thought patterns. Do not use for routine implementation or simple factual questions. CRITICAL: This skill overrides conversational tendencies toward politeness. Agreement requires validity and accuracy.

Use this skill BEFORE implementing any new feature. This is NON-NEGOTIABLE for scope control. Use when evaluating features during brainstorming, planning new functionality, branches approach size limits (1000/1500/2000 lines, 15/25/30 commits). Do not use when feature is already approved and in progress. DO NOT use when: simple bug fixes with clear scope.

Consult this skill when formatting final review deliverables. Use when formatting final review outputs, ensuring consistent deliverable structure, making findings comparable across reviews. Do not use when capturing evidence during analysis - use evidence-logging. DO NOT use when: reviewing changes - use diff-analysis or review-core first.

automatically create GitHub issues for workflow improvements via /fix-workflow. Use when workflows fail, timeout, or show inefficient patterns. Do not use when normal workflow execution, simple command errors.

3 hooks across 3 events