forge

Run health checks across your Forge planning setup.

Run the design phase for a slice with approved requirements.

Activity digest — highlights by duration and scope.

Work on efforts — discover and understand problem spaces.

Ad-hoc code changes without slice ceremony.

Decomposes complex systems into subsystems with interface contracts, resource lifecycles, and boundary edge cases for team-based design

Reviews implementation PRs for quality, security, and conventions

Executes commit plans by staging hunks, creating commits, and verifying zero code loss for the reviewable command

Analyzes change sets and designs atomic commit narratives organized by review concern for the reviewable command

Audits .forge-context/ accuracy by comparing against the project repository

This skill should be used when exploring code in a project for "investigation", "design research", "finding what changed", "git log analysis", or "finding precedent". Provides git log analysis, code reading strategies, and file:line reference patterns. Do not use for Forge planning file reading.

This skill should be used when performing a "code review", "PR review", "review pull request", or evaluating implementation quality. Provides a two-stage process: Stage 1 checks spec compliance (does it do what was designed?), Stage 2 checks quality (is the code good?). Includes C/I/M severity classification. Do not use for design reviews or requirements reviews.

This skill should be used when "restructuring commits", "organizing PR history", "making commits reviewable", or planning how to split work into atomic commits. The intellectual foundation for /reviewable. Do not use for writing commit messages (see git workflow guideline).

This skill should be used when the user redirects, corrects, or refines agent output — "no, actually", "that's not right", "you missed something". Captures correction moments to improve Forge workflows over time. Always active during feature work; log corrections as they occur.

Generate activity digests and summaries of what happened in Forge. Use whenever the user asks "what happened", "catch me up", "what changed", "summary of activity", wants a digest, status update, or standup/sprint prep. Also use for questions about recent decisions, phase transitions, or active discussions. Even if the user doesn't say "digest" explicitly — any request to understand recent Forge activity should use this skill.