github-publisher

Publish GitHub repositories with bilingual READMEs and validation checklists.

Updated Apr 10, 2026

Search Tags:#automation #publishing #github #validation #readme #repository #bilingual

Ready to run

npx skills add https://github.com/Glour/ai-office-v2 --skill github-publisher

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-publisher
Source: https://github.com/Glour/ai-office-v2/tree/main/skills/github-publisher
Command: npx skills add https://github.com/Glour/ai-office-v2 --skill github-publisher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repositories on GitHub are often created or updated with inconsistent readmes, missing validation checks, and mixed languages. This leads to confusion, maintenance overhead, and lower code quality.

Core Features & Use Cases

Unified README — English-first README with Russian translation and social links
Checklist Validation — enforces license, gitignore, and file presence for GitHub repos
Automated Publishing — creates or updates repos in a standardized format and structure
Use Case: Publish a new project or refresh an existing repo to a consistent, ready-to-share state

Quick Start

Publish a GitHub repository in a standardized format.

Frequently Asked Questions about github-publisher

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

FAQPage Schema

How do I standardize GitHub repository publishing with a consistent README and validation?▼

Automate bilingual README generation by creating an English-first README with a Russian translation and social links included. This ensures your repository maintains consistent documentation across both languages for a broader audience.

What validation checks are enforced for a GitHub repository before publishing?▼

Automated publishing creates or updates GitHub repositories in a standardized format and structure. It applies the unified bilingual README and validation checklist to refresh existing repos or publish new projects to a ready-to-share state.

Does this GitHub publishing approach work for updating existing repositories or only creating new ones?▼

This GitHub publishing approach works for both creating new repositories and updating existing ones. It applies standardized formatting, bilingual README generation, and validation checks to refresh any repo to a consistent, ready-to-share state.

Why do my GitHub repositories end up with inconsistent READMEs and missing validation checks?▼

Bilingual README generation should be applied when you need to publish or update a GitHub repository for an international audience. It creates an English-first README with Russian translation to enforce consistency across documentation.