Skip to main content
skill CX Codex

pre-publish-checker — Claude Code skill: checks before release

pre-publish-checker audits project files for profanity, internal links, sensitive paths, and unfinished development markers. Use it when preparing code or an extension for public release.

Apache-2.0 ★ 151 updated 2026-10-12

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add gemini-cli-extensions/sre
/plugin install sre-extension@sre
Open on GitHub

What pre-publish-checker does

The skill combines script-based checks with a manual review. It guides the agent through creating PUBLICATION_CHECKLIST.md from a template and checking listed files for offensive language, internal short links such as go/, local or company-specific paths, and unfinished-work markers. A flagged TODO should be resolved or moved to a tracking system, not erased just to clear the check.

Run the file checker with uv run -s skills/pre-publish-checker/scripts/check_file.py <file_path>; use python3 if uv is unavailable. To get a summary of outstanding items, run uv run -s skills/pre-publish-checker/scripts/summarize_checklist.py. The final stage calls for a manual professionalism and quality review, followed by checking every item in the checklist. Without uv, file checks can use python3, but the documented summary command uses uv.

A valid exception can be recorded in PUBLICATION_CHECKLIST.md with [Pass] and USER_BYPASS: <explanation>. The skill also recommends moving open TODO items into a tracking system and replacing their markers with issue links.

What it helps with

  • scan release files for profanity
  • catch internal links and machine-specific paths
  • build a project file checklist for review
  • resolve or track unfinished development markers
  • summarize the remaining publication checks

Example prompts for the agent

  • Audit this project before release for profanity, internal links, and sensitive paths.
  • Create PUBLICATION_CHECKLIST.md and check each listed file.
  • Summarize the remaining work in PUBLICATION_CHECKLIST.md.

How to install pre-publish-checker

1Plugin marketplace

/plugin marketplace add gemini-cli-extensions/sre
/plugin install sre-extension@sre

This installs the whole sre-extension plugin with all its skills

2Skills CLI (Vercel)

npx skills add gemini-cli-extensions/sre --skill pre-publish-checker -a claude-code

3Manually: put the files in place

~/.claude/skills/pre-publish-checker/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/pre-publish-checker/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about pre-publish-checker

How do I install pre-publish-checker in Claude Code?

Add the marketplace with /plugin marketplace add gemini-cli-extensions/sre, then install the skill with /plugin install sre-extension@sre.

What does pre-publish-checker do?

It guides a pre-release audit of project files. Scripts scan for profanity, internal links, sensitive paths, and unfinished-work markers; a manual pass covers professionalism and overall quality.

Can I run the checks without uv?

Yes. Run the file checker with python3 instead of uv, using skills/pre-publish-checker/scripts/check_file.py <file_path>. The documented checklist summary command uses uv.

Source text

SKILL.md · Apache-2.0
---
name: pre-publish-checker
description: 🐉 Thoroughly checks files for profanity, internal links, sensitive paths, and professionalism before publication. Use when preparing a codebase or extension for public release.
metadata:
  author: SRE Team
  version: 0.1.0
  status: draft
---

# Pre-Publish Checker

This skill guides you through a thorough audit of your project to ensure it meets publication standards. It combines automated script-based checks with a manual review workflow.

## Policies

1. **Do Not Simply Remove TODOs**: Do not delete `TODO` markers just to make the check pass. Instead: <!-- pre-publish-checker: ignore -->
    *   **Action them**: Resolve the task described.
    *   **Move them**: Transfer the `TODO` to a tracking system (e.g., GitHub Issues) and replace the marker with a link to the issue. <!-- pre-publish-checker: ignore -->
2. **User Bypass**: Any flagged issue can be bypassed if there is a valid reason. In `PUBLICATION_CHECKLIST.md`, mark the status as `[Pass]` and include the keyword `USER_BYPASS: <explanation>`.

## Workflow

### 1. Initialization

- List all relevant files: Markdown (.md), code files (.py, .js, .go, etc.), `justfile`, and `README`s.
- Create a `PUBLICATION_CHECKLIST.md` in the project root by copying the template from `references/checklist_template.md`.
- Populate the file list in the checklist.

### 2. Automated Audit
For each file in the checklist, run the automated check script:
```bash
uv run -s skills/pre-publish-checker/scripts/check_file.py <file_path>
```
*Note: If `uv` is not available, use `python3`.*

### 3. Iterative Review
- Process files one by one (or in small batches).
- Update the `PUBLICATION_CHECKLIST.md` with the status and any issues found.
- Fix issues as they are identified.
- For "long work", you can resume the process by reading the current state of `PUBLICATION_CHECKLIST.md`.
- **Get a Synopsis**: At any point, you can generate a quick summary of remaining work by running:
  ```bash
  uv run -s skills/pre-publish-checker/scripts/summarize_checklist.py
  ```
  *(Defaults to reading `PUBLICATION_CHECKLIST.md`)*

### 4. Final Verification
- Perform manual checks for "Google-bar professionalism" and overall quality.
- Ensure all boxes in `PUBLICATION_CHECKLIST.md` are checked.

## Check Categories

1. **Profanity**: Scans for common offensive language.
2. **Internal Links**: Finds internal shortlinks (e.g., `go/` links) which are not accessible outside.
3. **Internal Paths**: Identifies local machine or company-specific paths that reveal internal infrastructure.
4. **Professionalism**: Checks for development markers (e.g., "to-do", "fix-me") that should be resolved before release.

© SRE Team · Apache-2.0 · gemini-cli-extensions/sre

Similar skills

All skills for Security →

From the same set17

The whole set →
data-ingestion data-ingestion collects time-series points from CSV files or metric backends and converts them into standardized JSON. CX Codex +1 ★ 151repo stars cloud-logging Skill for analyzing Google Cloud Logging and Error Reporting. Processes large JSON logs from GCP and converts them to Apache format for efficient analysis. CX Codex +1 ★ 151repo stars gcp-slo-management gcp-slo-management finds services in Google Cloud Monitoring and creates availability or latency SLOs over the REST API, where gcloud has no command for it. CX Codex +1 ★ 151repo stars gcp-playbooks gcp-playbooks is a Claude Code skill with SRE playbooks for investigating GCP incidents and running mitigations across GKE and Cloud Run. CX Codex +1 ★ 151repo stars safe-sre-investigator safe-sre-investigator creates dedicated read-only service accounts for GCP and Kubernetes, then hands you gcloud and kubectl commands with a risk rating attached. CX Codex +1 ★ 151repo stars cloud-monitoring Interacts with Google Cloud Monitoring through MCP, rendering ASCII sparklines and concise CSV summaries to prevent context bloat. CX Codex +1 ★ 151repo stars postmortem-aggregator postmortem-aggregator turns Post Mortem files in a folder into incident statistics and updates POMO_AGGREGATED.md. Use it to spot recurring causes across incidents. CX Codex +1 ★ 151repo stars gcp-mcp-setup gcp-mcp-setup — a skill for Claude Code, Codex, and Gemini CLI that wires up Google Managed MCP servers (OneMCP) to your CLI environment. It enables APIs, generates an API key, and writes the MCP config to the right settings file. CX Codex +1 ★ 151repo stars

Project sponsors

Companies that keep this analytics open