t1k:sync-back

Push local skill edits to origin repositories as pull requests.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/tranvietanh0/StackTheRing --skill t1k-sync-back
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: t1k:sync-back
Source: https://github.com/tranvietanh0/StackTheRing/tree/main/.claude/skills/t1k-sync-back
Command: npx skills add https://github.com/tranvietanh0/StackTheRing --skill t1k-sync-back

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of pushing skill edits back to their origin kit repos as Pull Requests (PRs), streamlining the contribution and update process.

Core Features & Use Cases

  • PR Creation: Automatically creates PRs for skill edits, reducing manual effort.
  • Dry Run: Offers a dry run option to preview changes without actually creating PRs.
  • Force Option: Allows pushing changes without confirmation, useful for quick updates.
  • Use Case: After local modifications to a skill, use this Skill to automatically push the changes to the origin repository as a PR.

Quick Start

Run the t1k:sync-back skill to push your changes to the origin repository as a PR.

Frequently Asked Questions about t1k:sync-back

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

FAQPage Schema
How do I automate pushing local skill edits back to an origin repository as a PR?

To automate pushing local skill edits as a PR, you can use this Skill to automatically propagate your changes to the origin repository. It creates Pull Requests for your local modifications, streamlining the upstream contribution process.

Can I preview local repository changes before creating an upstream Pull Request?

Yes, you can preview changes before creating an upstream Pull Request by using the dry run option. This feature allows you to review your local modifications without actually pushing anything or opening a PR on GitHub.

Do I need GitHub access to automate PR creation for skill edits?

Yes, GitHub access is required to automate PR creation for skill edits. The process integrates with GitHub MCP tools to authenticate and push your local changes directly to the origin repository as Pull Requests.

What is the best way to propagate local updates to an upstream repository without manual confirmation?

The best way to propagate updates to an upstream repository without manual confirmation is using the force option. This bypasses confirmation prompts, allowing you to quickly push skill edits and automatically open a PR.

Why use an automated PR workflow for contributing skill modifications upstream?

Using an automated PR workflow for contributing skill modifications upstream ensures your repository state stays consistent. It eliminates manual effort by automatically packaging local edits and submitting them as Pull Requests to the origin repo.

Are there limitations when pushing local changes to origin repositories as Pull Requests?

A limitation when pushing local changes to origin repositories as PRs is the strict dependency on GitHub access and MCP tools. Without proper GitHub permissions, the automated PR creation and upstream propagation process will fail.