Resume unfinished work from a handoff document. The skill compares recorded progress and next steps with current files, branch state, and existing authorization, making differences and unknowns explicit before continuing.
Load a handoff document and resume work from where a previous session left off. Parses scope, file references, completed work, and next steps, then checks live state and existing authorization before proceeding.
Review the instructions the agent will receive before you install.
Read and load the handoff document at $ARGUMENTS[0].
Read the file at the provided path. If the path does not exist, list files in claudedocs/handoffs/ and ask the user which one to load.
Parse and confirm:
Reconcile with live state: Inspect the current branch, revision, relevant uncommitted changes, affected symbols, applicable decisions, and ownership. Compare them with the handoff. Revalidate checks needed for the next action when their evidence is stale or does not cover the current state. Done when material differences and remaining unknowns are explicit.
Resume within authorization: Summarize the task, evidence limits, and next action briefly. If the user already authorized continuation and the next action remains in scope, proceed. Ask only for missing decisions or authorization that materially affect the next action; wait before dependent work. Done when the next action is authorized or the precise blocker is reported.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.
Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.
Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.
Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.
Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.
Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.