parallel-work-check

Detects parallel remote commits on existing branches before starting local work.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/pandejesal/drone-nav-sar --skill parallel-work-check-pandejesal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-work-check
Source: https://github.com/pandejesal/drone-nav-sar/tree/main/.swarm/bundled-skills/parallel-work-check
Command: npx skills add https://github.com/pandejesal/drone-nav-sar --skill parallel-work-check-pandejesal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple agents or developers work on the same branch, starting work on a stale local copy wastes effort and creates conflicts. This Skill checks the remote branch state before you begin, so you never duplicate or overwrite work that already exists. ## Core Features & Use Cases - Remote Divergence Detection: Fetches the remote and compares local HEAD against remote HEAD to identify identical, ahead, behind, or diverged states. - Parallel Agent Identification: Inspects commit authors to detect work from other swarms or agents and defaults to preferring their results when they are superior. - Structured Decision Logging: Produces a PARALLEL WORK CHECK record documenting branch state, divergence, and a proceed/integrate/abandon decision with rationale. - Use Case: Before fixing PR feedback on an existing branch, run the check and discover a parallel agent already pushed 8 commits that resolve the issue cleanly, so you abandon your local approach instead of duplicating effort. ## Quick Start Before starting work on this existing branch, run the parallel work check to fetch the remote, compare commits, and document whether to proceed, integrate, or abandon my local changes.

Frequently Asked Questions about parallel-work-check

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

FAQPage Schema
How do I check if someone else pushed commits to my branch?

Fetch the remote for your branch, then compare the local HEAD hash with the remote HEAD hash. If they differ, run git log local..remote to read the new commit messages and see which files were touched.

How to avoid duplicate work when multiple AI agents use the same branch?

Run a parallel work check at session start and before planning: fetch the remote, compare HEADs, and inspect commit authors. If another agent's commits supersede your plan, reset to the remote and abandon your approach.

When should I run the parallel work check?

Run it at session start, before creating a plan for an existing branch, before dispatching the first coder task, and after any significant pause. It is not needed for a fresh branch you just created.

What should I do when local and remote branches have diverged?

Divergence means both sides have unique commits and requires integration via merge or rebase per team workflow. First evaluate whether the remote work supersedes yours; if it does, reset to remote instead of merging.

Why prefer a parallel agent's work over my own changes?

Parallel agents may have started earlier, had more iterations, or used different context and tools, often producing a superior result. The default stance is to prefer their work unless you can clearly articulate why your approach is better.