contribbot:daily-sync

Automate daily upstream repository synchronization into forked projects.

12|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/darkingtail/contribbot --skill contribbot-daily-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contribbot:daily-sync
Source: https://github.com/darkingtail/contribbot/tree/main/skills/daily-sync
Command: npx skills add https://github.com/darkingtail/contribbot --skill contribbot-daily-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of synchronizing changes from upstream repositories into your forked projects, ensuring your codebase stays up-to-date with minimal manual intervention.

Core Features & Use Cases

  • Automated Upstream Sync: Tracks and integrates new commits from specified upstream or fork sources.
  • Noise Reduction: Filters out non-essential commits like CI or dependency updates.
  • Commit Review Workflow: Allows users to review pending commits and decide whether to skip, create a todo, or link to an issue.
  • Mode-Based Logic: Adapts its workflow based on project configuration (none, fork, upstream, fork+upstream).

Quick Start

Run the daily sync for the darkingtail/antdv-next repository.

Frequently Asked Questions about contribbot:daily-sync

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

FAQPage Schema
How do I automate syncing upstream changes into a forked git repository?

You can review pending upstream commits through a dedicated workflow that lets you skip non-essential changes, create todos, or link commits to existing issues for tracked management.

How does noise reduction work when syncing upstream commits?

Noise reduction during upstream sync works by filtering out non-essential commits like CI configurations or dependency updates, ensuring your codebase only integrates meaningful changes.

Can I sync upstream changes for projects with multiple fork and upstream configurations?

Yes, you can sync upstream changes across multiple project modes including none, fork, upstream, and fork+upstream configurations, adapting the workflow to your specific repository setup.

What is the best way to review pending upstream commits before integrating them?

Reviewing pending upstream commits is handled through a built-in workflow allowing you to decide whether to skip noisy commits, create a todo task, or link the change to an issue.