rb-continue-project

To resume a multi-session coding project, this skill synthesizes project diaries, handoff notes, and git state into a coherent continuity brief. It automatically aggregates project history and current working environment data to reconstruct the exact project state without manual re-onboarding.

Maintaining continuity across development sessions requires aggregating git status, recent commits, and architecture documentation. This skill reads local project documentation and standard git tooling to reconcile the working environment and identify exactly where the previous session left off.

To check existing test levels and CI gates before continuing development, this skill recovers specific testing commands, coverage thresholds, and CI-equivalent gates. It ensures strict adherence to project quality requirements by aggregating test and CI awareness into the continuity brief.

This context recovery approach relies on synthesizing project diaries, handoff notes, and architecture documentation alongside git state. While it can inspect git status and recent commits, repositories lacking local project documentation will yield a less comprehensive continuity brief for multi-session tasks.

This project resumption workflow applies to mature repositories requiring multi-session coding tasks. It requires access to local project documentation and standard git tooling to verify the current working environment and reconstruct the project state accurately.

Automated context aggregation for complex project workflows depends on the existence of updated handoff notes and project diaries. If local documentation is outdated or missing, the synthesized continuity brief may not fully capture architectural decisions or project-specific workflows needed for strict adherence.