public-release-gate
Skill1 starsChanged 2 months agoMITView on GitHub
Review a public repository release across version and tag consistency, final build artifacts, archives, secrets and internal material, third-party licenses, production response headers, and GitHub Release attachments. Use when the user asks to publish, create a tag or Release, verify a launch, or run the complete public-release gate, adapting checks to the project's configuration.
In this repository7 other files it gives its agents.
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 14 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Treat a Release as a separate deliverable.
- Distinctive: line 19
Keep the review read-only by default.
- Distinctive: line 26
Before starting, identify the repository root, target version and tag, final artifact paths, third-party resource inventory, production …
- Very specific: line 55
Check that package.json and lockfiles, or the project's version files, agree with the README, CHANGELOG, Release Notes, and tag.
- Distinctive: line 59
Check for secrets, personal or customer data, internal business or legal material, private model or service configuration, and files that …
- Distinctive: line 65
After deployment, check HTTPS, HTTP status, key static entry points, CSP, HSTS, X-Frame-Options, and other project-required response …
- Distinctive: line 67
Before creating a GitHub Release, verify the tag, Release page, and every attachment.
- Distinctive: line 70
When database migrations, edge functions, or external configuration are involved, confirm production state separately.
- Very specific: line 76
Prefer the project's existing release:check.
- Distinctive: line 99
Keep project-specific details in the configuration, such as Supabase migrations, a Vercel production URL, Piper resources, and required …
- Distinctive: line 101
Do not copy one project's assumptions into another.
- Distinctive: line 103
Prefer to provide these commands or equivalent entry points:
- Distinctive: line 110
When no automated entry point exists, perform the same checks manually and record the evidence in the PR or Release Notes.
- Distinctive: line 116
If you find a secret, personal data, internal material, a missing license, or an artifact mismatch, stop the release and record the exact …
- Very specific: line 119
If the production URL, GitHub Release permission, deployment state, or external configuration is unavailable, mark the gate BLOCKED.
- Very specific: line 122
After a fix, rerun the failed check and recheck affected versions, artifact hashes, and attachments.
- Distinctive: line 124
Treat exposed secrets or personal data as a security incident, rotate the credentials, and retain an incident record.
- Distinctive: line 138
Treat the following requests as full triggers:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Public Release Gate
Treat a Release as a separate deliverable. Repository commit checks do not
constitute a Release review; inspect the source, final artifacts, release page,
and deployment state together. The sibling public-repo-git-gate skill owns
the public-content and branch gates for commit, push, and PR operations. Do not
repeat this skill's artifact checks for an ordinary commit.
This skill is a manual review workflow. A passing script or CI job alone does not prove every Release condition. Reuse the project's existing automated checks first, then manually verify final artifacts, the hosting platform, and production. Mark the gate as passed only when the required evidence exists.
Keep the review read-only by default. Creating a tag or GitHub Release, uploading attachments, changing production configuration, or deploying each requires explicit user authorization. Passing this gate does not authorize any of those actions.
Inputs and output
Before starting, identify the repository root, target version and tag, final artifact paths, third-party resource inventory, production URL, and project-specific configuration.
Return a structured record containing at least:
Release gate: PASS | BLOCKED | FAILED
Repository:
Version / tag:
Build and artifacts:
Publicity and sensitive-data scan:
Third-party notices:
Deployment and response headers:
Release page and attachments:
Evidence:
Skipped checks / residual risks:PASS means that all required evidence was checked. BLOCKED means that an
external state, permission, or user decision is missing. FAILED means that
the review found a problem. Neither non-passing state permits creating a tag,
GitHub Release, or continuing deployment.
Workflow
- Identify repository visibility, technology stack, build commands, artifact directories, version sources, third-party resources, and deployment entry points.
- Check that
package.jsonand lockfiles, or the project's version files, agree with the README, CHANGELOG, Release Notes, and tag. - Build the final artifacts from a clean state. Scan both the artifact directories and final archives; do not scan only the source tree.
- Check for secrets, personal or customer data, internal business or legal material, private model or service configuration, and files that do not need to be public.
- For vendored code, models, WASM, fonts, and media, verify the source, version or commit, license, redistribution terms, and SHA-256 individually. The license inventory must match the final resources.
- After deployment, check HTTPS, HTTP status, key static entry points, CSP, HSTS, X-Frame-Options, and other project-required response headers.
- Before creating a GitHub Release, verify the tag, Release page, and every attachment. Attachments must come from scanned final artifacts; calculate and record their SHA-256 values.
- When database migrations, edge functions, or external configuration are involved, confirm production state separately. Passing CI does not prove that a production migration ran.
Reuse project checks
Prefer the project's existing release:check. If none exists, create
release-gate.config.json in the project root with at least:
{
"versionFiles": ["package.json"],
"artifactPaths": ["dist"],
"vendoredPaths": [],
"noticeFiles": ["THIRD_PARTY_NOTICES.md"],
"requireDeploymentChecklist": true,
"deploymentChecklist": "docs/release-checklist.md",
"production": {
"requiredHeaders": [],
"forbiddenHeaderValues": [],
"paths": ["/"]
}
}This is a cross-project convention example, not a universal validation
schema. The project's own release:check must validate its actual fields and
paths.
Keep project-specific details in the configuration, such as Supabase migrations, a Vercel production URL, Piper resources, and required headers. Do not copy one project's assumptions into another.
Prefer to provide these commands or equivalent entry points:
npm run verify # Source, tests, and build
npm run release:check # Release metadata, artifacts, licenses, and deployment checksWhen no automated entry point exists, perform the same checks manually and record the evidence in the PR or Release Notes. Stop the release on any failed check; do not create the Release first and explain afterward.
Failure, blocking, and recovery
- If you find a secret, personal data, internal material, a missing license, or an artifact mismatch, stop the release and record the exact path, attachment, or check item.
- If the production URL, GitHub Release permission, deployment state, or
external configuration is unavailable, mark the gate
BLOCKED. Do not use a successful local build as a substitute for external evidence. - After a fix, rerun the failed check and recheck affected versions, artifact
hashes, and attachments. Do not reuse an old
PASSrecord unchanged. - Treat exposed secrets or personal data as a security incident, rotate the credentials, and retain an incident record. Merely deleting a file or rewriting history does not prove that the risk is gone.
Platform boundaries
Version, build, artifact, and license checks apply across languages and build systems, but use the commands defined by the project. GitHub Release, HTTP header, and production-deployment checks depend on the relevant hosting platform. Do not describe an untested platform CLI, Preview environment, or local server result as production verification.
Trigger phrases
Treat the following requests as full triggers:
- "Check this Release against the complete public-repository gate."
- "Can this tag be released?"
- "Review the final installer/archive and GitHub Release."
- "Verify this version after launch."
An ordinary request to "check a commit" covers only the commit/PR gate. When the user mentions a Release, tag, installer, store package, deployment, or launch, use this skill's complete workflow.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

