ljg-push

Push updated ljg-* skills to the ljg-skills repository with dual-branch sync and version bumps.

Updated Feb 2, 2016
One-click install
npx skills add https://github.com/zjykzk/blog --skill ljg-push-zjykzk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ljg-push
Source: https://github.com/zjykzk/blog/tree/main/.agents/skills/ljg-push
Command: npx skills add https://github.com/zjykzk/blog --skill ljg-push-zjykzk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ljg-push helps teams synchronize updated ljg-* skills to the central ljg-skills repo, ensuring master and md branches stay aligned for organized distribution.

Core Features & Use Cases

  • Unified syncing: push local updates to the repo in master (org-mode) and automatically convert to md on the md branch for consistent markdown documentation.
  • Version & consistency guarantees: automatically bump patch versions in plugin.json and marketplace.json and keep README in sync to prevent drift.
  • Safe, auditable workflow: performs pre-push checks, git operations, and reports changes for review.

Quick Start

Run the /ljg-push command to push updated ljg-* skills to the ljg-skills repository and create/update both master and md branches.

Frequently Asked Questions about ljg-push

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

FAQPage Schema
How do I sync local skill updates to a git repository with both markdown and org-mode branches?

To sync local skill updates, you can push changes to a central repository and manage a two-branch workflow. This process automatically converts org-mode master branch files to markdown on an md branch for consistent documentation.

Can I automatically bump patch versions in plugin.json and marketplace.json when pushing skill updates?

Yes, you can automatically bump patch versions in plugin.json and marketplace.json during the sync workflow. This version bumping guarantees consistency and prevents documentation drift when pushing updated skills.

What is the best way to keep README files in sync when pushing updated skills to a repository?

Keeping README files in sync requires validating the README before pushing and syncing changes with rsync. This ensures your markdown documentation stays aligned and prevents drift across master and md branches.

How does automatic markdown conversion work for a two-branch git workflow?

Automatic markdown conversion works by pushing org-mode content to a master branch and converting it to markdown on an md branch. It uses rsync to sync changes and performs pre-push checks to report differences for review.

Do I need any dependencies to run pre-push checks and rsync for skill synchronization?

No dependencies are required to run pre-push checks and rsync for skill synchronization. The workflow operates independently to validate READMEs, sync changes, bump versions, and manage git operations safely.