skills.rest
Juhwa-Lee1023
Juhwa-Lee1023COMMUNITY
Explore all skills by this author →
GitHub

pre-publish-review

Analyze git logs, diffs, and package metadata to produce a release gate report.

Updated Apr 15, 2026
Search Tags:#git#release-management#quality-assurance#copilot-cli#pre-publish#release-review
One-click install
npx skills add https://github.com/Juhwa-Lee1023/x-for-github-copilot --skill pre-publish-review-juhwa-lee1023
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-publish-review
Source: https://github.com/Juhwa-Lee1023/x-for-github-copilot/tree/main/source/skills/pre-publish-review
Command: npx skills add https://github.com/Juhwa-Lee1023/x-for-github-copilot --skill pre-publish-review-juhwa-lee1023

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multi-pass pre-publish review for X for GitHub Copilot to enforce a structured release gate before tagging or publishing.

Core Features & Use Cases

  • Guides a release review by comparing the last version tag, release-branch points, or origin/main to surface gaps.
  • Inspects git logs, diffs, and package metadata to surface correctness, compatibility, and risk signals.
  • Produces a go/no-go summary with explicit blockers and non-blocking risks.

Quick Start

Run the pre-publish-review workflow on the current changes to generate a release gate report with scope, blockers, and a go/no-go recommendation.

Frequently Asked Questions about pre-publish-review

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

FAQPage Schema
How do I automate a pre-publish review for GitHub Copilot releases?▼

A multi-pass pre-publish review analyzes git logs, diffs, and package metadata to surface release risks and blockers before tagging, generating a structured go/no-go publish decision.

What is a structured release gate and when do I need it for version tagging?▼

A structured release gate compares the last version tag, release branch points, or origin/main to identify gaps and blockers before publishing, ensuring release scope and version bump correctness.

How do I determine the recommended version bump from git history before publishing?▼

Analyze git logs, diffs, and package metadata to evaluate the release scope and generate a recommended version bump, surfacing the required semantic version increment for your changes.

Can I use git diff analysis to find blockers and non-blocking risks before a release?▼

Yes, git diff analysis inspects changes between the last version tag and origin/main to explicitly identify blockers and non-blocking risks, producing a structured go/no-go summary.

Does the pre-publish review workflow work with Copilot CLI and no external dependencies?▼

Yes, the pre-publish review workflow runs via Copilot CLI with no external dependencies, directly analyzing git history and package metadata to enforce release quality assurance.

What are the limitations of relying on automated git log analysis for release quality assurance?▼

Automated git log analysis generates risk signals and a recommended go/no-go decision, but requires human judgment to evaluate surfaced blockers and non-blocking risks before final publishing.

Related Skills

Explore More Software Engineering Skills→
gmcabritagmcabrita
6

update-changelog

Aggregate unreleased Git commits into the CHANGELOG.md Unreleased section.

Community
Intermediate
vincent119vincent119

release-workflow

Automate standardized release management across Go, Python, Node.js, Bash, and YAML repositories.

Community
Intermediate
DevelopersGlobalDevelopersGlobal
65

ci-cd-pipelines

Automate CI/CD pipelines with quality gates and deployment processes.

Official
Advanced
Veloxia-agencyVeloxia-agency

ship-gate

Audit codebases for pre-production shipping risks across eight release-readiness categories.

Community
Advanced