skills.rest
kriscendobot
kriscendobotCOMMUNITY
Explore all skills by this author →
GitHub

pr-handoff

Migrate pull requests from a garden-side fork to an upstream repository with attribution rewrite and metadata sanitization.

3|2|Updated May 12, 2026
Search Tags:#automation#git#workflow#pull request#governance#attribution
One-click install
npx skills add https://github.com/kriscendobot/garden --skill pr-handoff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-handoff
Source: https://github.com/kriscendobot/garden/tree/main/skills/pr-handoff
Command: npx skills add https://github.com/kriscendobot/garden --skill pr-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the complex, multi-step process of transitioning a garden-side pull request into an upstream repository while maintaining strict attribution, trailer discipline, and branch-protection compliance.

Core Features & Use Cases

  • Attribution Rewrite: Automatically updates commit authors and committers to the correct human identity while preserving multi-author history where required.
  • Trailer & Metadata Sanitization: Strips bot-specific trailers and fork-side references to ensure the upstream PR meets professional governance standards.
  • Multi-Shape Ferrying: Supports first-time PR creation, force-push re-ferries, and fast-forward appends to maintain review history and approval persistence.

Quick Start

Use the pr-handoff skill to ferry the current garden-side pull request to the upstream repository using the appropriate procedure shape.

Frequently Asked Questions about pr-handoff

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

FAQPage Schema
How do I rewrite commit attribution when migrating a pull request to an upstream repository?▼

Rewriting commit attribution during a pull request migration updates authors and committers to the correct human identity while preserving multi-author history. This ensures agent-generated work transitions cleanly into human-maintained upstream projects.

What is the best way to sanitize fork-side metadata and bot trailers before a pull request handoff?▼

Sanitizing fork-side metadata strips bot-specific trailers and fork-side references from commits before an upstream pull request handoff. This process ensures the migrated PR meets professional upstream governance and branch-protection standards.

How do I preserve pull request approvals when force-pushing to an upstream governance repository?▼

Preserving pull request approvals during an upstream handoff relies on fast-forward appends and specific re-ferry procedures. These multi-shape ferrying techniques maintain review history and approval persistence across repository migrations.

When do I need to transition agent-generated work into a human-maintained upstream project?▼

Transitioning agent-generated work into a human-maintained upstream project is needed when applying automated workflows to software engineering. It satisfies strict technical requirements for identity-switched commits, trailer-strip discipline, and approval-preserving merges.

Does this pull request migration workflow support fast-forward merges without losing commit history?▼

Yes, this pull request migration workflow supports fast-forward merges by appending commits directly to the upstream branch. It preserves multi-author history and maintains approval persistence without discarding prior review state.

Why does my upstream pull request fail branch protection after migrating from a fork?▼

An upstream pull request may fail branch protection after a fork migration due to unsanitized bot trailers or incorrect commit attribution. Applying trailer-strip discipline and identity-switched commits resolves these governance violations.

Related Skills

Explore More Software Engineering Skills→
Knuckles-TeamKnuckles-Team
2

git-config

Read, set, and validate Git config values across global and local scopes.

Official
Intermediate
adaptive-enforcement-labadaptive-enforcement-lab
3

required-status-checks

Enforce required CI status checks on GitHub pull requests before merge.

Official
Intermediate
sparkfabriksparkfabrik
3

sf-commit-convention

Enforce SparkFabrik commit message and branch naming conventions across git operations.

Official
Advanced
Knuckles-TeamKnuckles-Team
2

git-advanced

Automate Git history fixes using rebase, cherry-pick, and bisect workflows.

Official
Advanced