handle

Attach to a branch or PR and run the plan or review lane it requires.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/vzakharov/vovazakharov.com --skill handle-vzakharov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handle
Source: https://github.com/vzakharov/vovazakharov.com/tree/main/.claude/skills/handle
Command: npx skills add https://github.com/vzakharov/vovazakharov.com --skill handle-vzakharov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Resuming work on an existing branch or pull request is ambiguous: the branch might hold a draft plan awaiting approval, unanswered review feedback, or shipped code needing fixes. This Skill removes that guesswork by inspecting the branch and dispatching the correct workflow lane automatically. ## Core Features & Use Cases - Automatic lane detection: Reads the branch's plan files and PR review state to decide between a plan lane (implementing an approved plan) and a review lane (addressing unanswered feedback), including the combined case of a draft plan under review. - PR feedback triage: Exports the PR via a script, applies a thread-tail test to find guidance nobody has answered, commits the export snapshot, and replies on GitHub to every addressed comment. - Optional finalization: Runs land-prep only when the invocation includes and finalize, and defers merging to a separate explicit step. - Use Case: After a compaction boundary, type /handle with no arguments to re-attach to the current branch, pick up unanswered review comments, address them, and push the result. ## Quick Start Type /handle followed by a branch name, PR number, or PR URL to pick up that branch and run whatever work it needs.

Frequently Asked Questions about handle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume work on an existing branch or PR?

Invoke /handle with a branch name, PR number, or PR URL, or with no argument to target the currently checked-out branch. The skill attaches to the branch, reads what it needs, and runs the appropriate lane automatically.

How does the skill decide between implementing a plan and addressing review feedback?

It checks docs/plans/ for non-completed plan files and inspects PR review threads for unanswered guidance. A draft plan with feedback triggers plan revision, feedback alone triggers the review lane, and a draft plan without feedback triggers implementation.

Does /handle merge or finalize the pull request automatically?

No. Finalization runs only when the invocation includes the `and finalize` flag, and merging is never performed. An `and merge` flag is treated as finalize only, with the actual merge deferred to a separate /finalize command.

What happens when /handle finds no work on the branch?

If no plan lane or review lane fires and no extra guidance was given, the skill stops and reports the branch state — last commit, PR status, and plan files — then asks the operator for direction rather than inventing work.

Why does the skill export and commit the PR before addressing feedback?

The export is a fresh snapshot of the PR's current state, since review comments may have arrived since any prior export. Committing it makes the next re-export comparable via git diff and records what the agent was reacting to.