setup-downstream-fork

Create and maintain downstream forks with LLM-guided conflict resolution and cruise-control syncing.

3|Updated Jan 14, 2014
One-click install
npx skills add https://github.com/prateek/dotfiles --skill setup-downstream-fork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-downstream-fork
Source: https://github.com/prateek/dotfiles/tree/main/.agents/skills/setup-downstream-fork
Command: npx skills add https://github.com/prateek/dotfiles --skill setup-downstream-fork

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill automates the end-to-end setup and maintenance of a downstream fork that tracks upstream with LLM-driven conflict resolution, enabling reliable automation and governance while keeping upstream changes integrated.

Core Features & Use Cases

  • Automates greenfield fork creation from upstream; creates and manages a .fork namespace; wires GitHub Actions and initial sync
  • Supports doctor audits to detect drift and guide automated repairs
  • Provides a cruise-control workflow that continuously syncs with upstream and applies patches via LLM resolution
  • Facilitates secure secret management and CI gating for downstream forks

Quick Start

Launch the setup flow to clone upstream, scaffold .fork, configure secrets, and trigger the first downstream sync.

Frequently Asked Questions about setup-downstream-fork

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

FAQPage Schema
How do I automate downstream fork setup and continuous syncing with an upstream repository?

This skill orchestrates a greenfield workflow to clone upstream, scaffold a .fork namespace, configure GitHub Actions, and trigger the first downstream sync for automated fork maintenance.

What is LLM-guided conflict resolution for maintaining a downstream fork?

LLM-guided conflict resolution uses language models to automatically resolve merge conflicts during upstream syncs, applying patches while keeping downstream changes integrated and recoverable via rollback.

How do I detect and repair drift between my downstream fork and upstream project?

The doctor audit mode detects drift between your downstream fork and upstream, then guides automated repairs by evaluating gate-checks and enforcing a reproducible fork layout to restore alignment.

Can I use GitHub Actions to enforce CI gating and secret management for downstream forks?

Yes, this skill wires GitHub Actions to enforce CI gate-checks and facilitates secure secret management, ensuring downstream forks maintain governance and reliable automation during continuous upstream syncing.

What's the best way to keep a downstream fork continuously synced with upstream changes?

The cruise-control workflow continuously syncs with upstream and applies patches via LLM resolution, providing a recoverable rollback plan to maintain reliable upstream integration without manual intervention.