do

Coordinates planning, shallow cloning, QA, and PR creation across multiple repositories.

17|4|Updated Feb 9, 2026

Search Tags:#planning #orchestration #multi-repo #code-review #pull-requests #issue-management

Ready to run

npx skills add https://github.com/chardigio/pappardelle --skill do-chardigio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: do
Source: https://github.com/chardigio/pappardelle/tree/main/examples/skills/do-multi-repo
Command: npx skills add https://github.com/chardigio/pappardelle --skill do-chardigio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating end-to-end issue implementation across multiple repositories, ensuring planning, code changes, testing, and governance occur in a synchronized workflow.

Core Features & Use Cases

End-to-end multi-repo orchestration: coordinates planning, shallow cloning, coding, QA, and PR creation across all affected repos.
Cross-team agent coordination: assigns roles and tracks progress per repository to prevent conflicts.
Efficient repo cloning: uses shallow clones to keep initialization fast while maintaining traceability and rollback options.
Governance and traceability: generates per-repo PRs alongside a coordinating parent reference that links changes.

Quick Start

Provide a clear, end-to-end implementation plan across multiple repositories for a given issue.

Frequently Asked Questions about do

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

FAQPage Schema

How do I manage multi-repo issue implementation across several components?▼

Multi-repo issue implementation is managed by orchestrating planning, shallow cloning, coding, QA, and pull request creation across all affected repositories. This coordination assigns roles per repository and generates a parent reference linking the cross-repo changes.

What's the best way to orchestrate pull requests for a cross-repo code review?▼

Orchestrating pull requests for cross-repo code review involves generating per-repo PRs alongside a coordinating parent reference. This links all changes together, ensuring synchronized governance and traceability across multiple repositories.

How does shallow cloning work for multi-repo code orchestration?▼

Shallow cloning for multi-repo orchestration keeps repository initialization fast while maintaining traceability and rollback options. It efficiently fetches only the necessary repository depth for coordinated coding and QA tasks.

Can I coordinate cross-team agent assignments for multi-repo workflows?▼

Cross-team agent coordination is supported by assigning roles and tracking progress per repository. This prevents conflicts during end-to-end issue implementation across multiple components and teams.

When do I need end-to-end multi-repo orchestration for issue management?▼

End-to-end multi-repo orchestration is needed when an issue spans several components or teams. It ensures synchronized planning, code changes, testing, and governance across all affected repositories through deterministic tasks.

Does multi-repo orchestration support deterministic task generation for planning?▼

Multi-repo orchestration supports deterministic task generation to specify inputs and step-by-step execution. This governance mechanism coordinates planning, coding, and pull request workflows across all repositories.