skills.rest
levnikolaevich
levnikolaevichCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ln-62-repository-publisher

Validates, commits, pushes, and remotely verifies authorized repository changes.

556|83|Updated Oct 24, 2025
Search Tags:#Git#push#Validation#Deployment#ci verification#repository publishing#Commit
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-62-repository-publisher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ln-62-repository-publisher
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/plugins/maintainer-suite/skills/ln-62-repository-publisher
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-62-repository-publisher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing code changes involves many failure points: staging unrelated files, skipping validation, pushing without checking remote divergence, and assuming a push means CI and deployment succeeded. This Skill enforces an evidence-based checklist so only authorized, validated changes are published and remotely verified.

Core Features & Use Cases

  • Scoped Staging and Commit: Inspects diffs, excludes unrelated user changes, removes secrets and artifacts, and matches the repository's commit-message convention.
  • Validation Routing: Runs repository-native validators, host-native strict validators, and only the checks required by the changed surfaces before committing.
  • Remote Verification: Confirms the pushed commit via Git and hosting APIs, watches CI runs, verifies deployments and clean-source installs, and returns a PUBLISHED, PARTIAL, or BLOCKED verdict.
  • Use Case: After updating a plugin marketplace catalog, use this Skill to validate the manifests, commit only the intended files, push to the authorized branch, watch CI, and verify the live site before reporting completion.

Quick Start

Use the repository publisher skill to validate, commit, and push my approved changes to the main branch, then verify CI and the deployed site.

Frequently Asked Questions about ln-62-repository-publisher

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

FAQPage Schema
How do I safely commit and push only approved changes in Git?▼

Review git status and diffs first, stage explicit paths instead of the whole worktree when changes are mixed, and exclude unrelated user modifications. This Skill enforces that workflow with a checklist covering staging, commit-message conventions, and push authorization.

How to verify a pushed commit actually deployed successfully?▼

Confirm the remote branch resolves to the pushed SHA using both Git and the hosting API, then watch required CI runs to completion. For static sites, verify live content with a cache-busting request; a successful push alone is not proof of deployment.

What should I check before committing changes to a repository?▼

Check staged and unstaged diffs, untracked files, deletions, and generated files, then run repository-native validators for changed surfaces. Also confirm whether documentation, catalogs, or installation commands need matching updates before committing.

Does this skill create releases, tags, or pull requests?▼

No. The skill never creates releases, tags, package publications, discussions, or pull requests unless explicitly requested. It handles only commit, push, and remote verification of authorized changes.

What happens when local and remote Git branches have diverged?▼

The skill stops and reports the commits on both sides instead of force-pushing or rewriting history. Publication returns a BLOCKED verdict until the divergence is resolved with user direction.

Why does a successful git push not mean publication succeeded?▼

A push only updates the remote branch; CI pipelines, marketplace refreshes, and site deployments run asynchronously and can fail independently. The skill requires observable remote evidence before returning a PUBLISHED verdict.

Related Skills

Explore More Software Engineering Skills→
swissarmyhammerswissarmyhammer
15

double-check

Review recent code changes for compilation errors and requirement alignment.

Official
Intermediate
gittowergittower
413

full-release

Orchestrate a Git-based software release from version preparation to published verification.

Official
Advanced
highflame-aihighflame-ai
4

doc-drift

Extract public surface changes from git diffs to audit documentation drift.

Official
Advanced
redisredis
8.7k

git-safety

Block unsafe Git operations on protected branches during commits, pushes, merges, rebases, resets, and deletions.

Official
Basic