agent-handoff

Create a canonical AGENTS.md file with compatible shims for multiple AI coding tools.

Updated Jul 5, 2026
One-click install
npx skills add https://github.com/kazhiramatsu/agent-handoff --skill agent-handoff-kazhiramatsu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-handoff
Source: https://github.com/kazhiramatsu/agent-handoff/tree/main
Command: npx skills add https://github.com/kazhiramatsu/agent-handoff --skill agent-handoff-kazhiramatsu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the drift caused by maintaining separate instruction files for different AI coding agents, so one project can be handed off without rewriting or resynchronizing context.

Core Features & Use Cases

  • Canonical project context: Establishes a single AGENTS.md as the source of truth for repo instructions.
  • Cross-tool compatibility: Sets up thin shims so tools like Claude Code, Cursor, Codex, Copilot, Gemini CLI, Aider, Windsurf, and Zed can all read the same guidance.
  • Idempotent setup: Reuses existing instruction files when present and avoids duplicating content or creating divergent copies.
  • Use case: Use this Skill when handing a repository to another agent, standardizing project instructions, or syncing context across multiple coding tools.

Quick Start

Ask the assistant to set up AGENTS.md and compatible shims so this project can be read consistently by every AI coding agent.

Frequently Asked Questions about agent-handoff

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

FAQPage Schema
How do I share project context across multiple AI coding agents like Claude Code and Cursor?

Sharing project context across AI coding agents requires establishing a single AGENTS.md file as the canonical source of truth, then adding thin symlinks or one-line configs so tools like Claude Code, Cursor, and Gemini CLI read identical instructions.

What is the best way to prevent instruction drift when handing off a repository between AI tools?

Preventing instruction drift during repository handoff involves eliminating divergent instruction files and maintaining one AGENTS.md file, ensuring every AI coding tool receives identical project context without rewriting or resynchronizing.

Does setting up an AGENTS.md file overwrite my existing Copilot or Codex instructions?

Setting up an AGENTS.md file does not overwrite existing instructions because the setup is idempotent, reusing current instruction files when present and avoiding duplicated content or divergent copies across compatible agents.

Can I use one AGENTS.md file to standardize instructions for Aider, Windsurf, and Zed simultaneously?

You can use one AGENTS.md file to standardize instructions for Aider, Windsurf, and Zed simultaneously by configuring thin shims that allow all these compatible AI coding agents to read the same project guidance.

How do I sync project context across multiple coding tools without maintaining duplicate files?

You sync project context without duplicate files by creating a canonical AGENTS.md and applying optional symlinks or one-line configs, which removes the need to maintain separate instruction files for different AI agents.