unitwork

Bulk resolve GitHub PR comments using checkpoint-based verification flow

First-time setup for Unit Work - check dependencies, configure Hindsight bank, explore codebase

Browser automation using Vercel's agent-browser CLI. Use for web interaction, form filling, screenshots, scraping, and UI/backend verification. Supports ref-based selection, parallel sessions, and headed debugging. Includes verification workflows with confidence assessment. Triggers on: browse website, fill form, click button, take screenshot, scrape page, web automation, UI verification.

Extract and store learnings to Hindsight memory and local documentation

Autonomously fix failing CI by cycling through analyze → fix → commit → push → verify

Use this agent to analyze the downstream impact of resolving a merge/rebase conflict. This agent identifies affected tests, dependent files, and behavioral implications of different resolution approaches.

Use this agent to analyze the intent behind each branch's changes in a merge conflict. This agent determines whether conflicts are purely textual (same goal, different implementation) or semantic (conflicting goals).

Use this agent for codebase exploration with memory integration. This agent recalls prior exploration findings from Hindsight, validates key file locations still exist, explores the codebase, and retains summarized findings including traversal strategies. Use instead of the standard Explore agent when you want exploration results to compound across sessions. Examples: - <example> Context: The user needs to understand where authentication code lives in a new codebase. user: "I need to find where authentication is implemented" assistant: "I'll use the memory-aware-explore agent to find authentication code and document the findings for future sessions." <commentary> Use memory-aware-explore when exploration results should be retained for future sessions. </commentary> </example> - <example> Context: Planning a feature that requires understanding existing patterns. user: "I'm planning to add a new API endpoint" assistant: "Let me explore the codebase for existing API patterns. I'll use memory-aware-explore so we don't repeat this exploration next time." <commentary> Memory-aware exploration compounds knowledge - findings from this session inform future sessions. </commentary> </example>

Use this agent to review a draft plan for technical feasibility issues. This agent identifies impossible or blocked units, unclear verification strategies, hidden dependencies, unrealistic confidence estimates, and units too large for a single session. Should be invoked during /uw:plan after draft plan creation. Examples: - <example> Context: Reviewing a draft plan with a unit that depends on an external API. user: "Check if this plan is technically feasible" assistant: "I'll analyze each unit for blockers, dependencies, and verification clarity." <commentary> Use feasibility-validator to catch blockers before implementation starts. </commentary> </example>

Use this agent to review a draft plan for information gaps that would require investigation during implementation. This agent identifies unclear requirements, missing API contracts, unspecified edge cases, and ambiguous specifications. Should be invoked during /uw:plan after draft plan creation. Examples: - <example> Context: Reviewing a draft plan for a new feature. user: "Check this plan for gaps that would block implementation" assistant: "I'll analyze the plan for missing information, unclear requirements, and unspecified edge cases." <commentary> Use gap-detector agent to find gaps before presenting plan to user. </commentary> </example>

This skill should be used when reviewing code or running /uw:review. It contains 47 issue patterns with severity tiers, team standards to enforce, and implementation checklists for the Unit Work review system.

This skill should be used when implementing features with human-in-the-loop verification. It provides the core Unit Work methodology including checkpoint-based development, confidence assessment, memory integration with Hindsight, and verification strategies. Use this skill for planning features, executing with checkpoints, reviewing code, and compounding learnings.