publish-quality

Execute pre-publish security and compliance checks on code repositories.

Updated Aug 23, 2026

Search Tags:#code quality #security #compliance #vulnerability audit #pre-publish #secrets scanning

Ready to run

npx skills add https://github.com/RedBeret/agent-skill-catalog --skill publish-quality

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: publish-quality
Source: https://github.com/RedBeret/agent-skill-catalog/tree/main/skills/publish-quality
Command: npx skills add https://github.com/RedBeret/agent-skill-catalog --skill publish-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill acts as a critical pre-publish quality gate, preventing sensitive information, PII, or vulnerabilities from being exposed in public code repositories.

Core Features & Use Cases

Comprehensive Checklist: Covers secrets scanning, PII detection, license compliance, dependency audits, and more.
Automated Checks: Provides commands and patterns to identify potential issues.
Use Case: Before pushing a new feature branch to a public GitHub repository, run this Skill to ensure no API keys were accidentally committed and that all dependencies are secure.

Quick Start

Run the publish-quality skill to perform a pre-publish security and compliance check on the current repository.

Frequently Asked Questions about publish-quality

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

FAQPage Schema

How do I scan my repository for secrets and PII before pushing to public?▼

A pre-publish quality gate scans your repository for secrets and PII by executing an automated checklist of security checks. This process identifies exposed API keys and personal data to prevent accidental public disclosure before pushing code.

What is a pre-publish quality gate for code repositories?▼

A pre-publish quality gate is a security and compliance checkpoint executed before code is made public. It validates repository integrity by running checks for secrets, PII, license compliance, and dependency vulnerabilities to ensure secure code release and regulatory adherence.

How do I audit dependency vulnerabilities before making my code public?▼

You audit dependency vulnerabilities before making code public by running a pre-publish quality gate that performs dependency vulnerability audits. This check identifies known risks in your project dependencies to ensure production-ready compliance.

Does a pre-publish security check cover license compliance and git history?▼

Yes, a pre-publish security check covers both license compliance and git history integrity. These checks are executed together with secrets scanning and PII detection to address regulatory adherence and prevent sensitive data exposure in git logs.

Can I use automated compliance checks for secure code release on any repository?▼

You can use automated compliance checks for secure code release on any repository requiring pre-publish validation. The quality gate executes security checks including secrets scanning and dependency audits without requiring external dependencies or specific platform configurations.