agentleFS
kunalsurikunalsuri/1000x-Agent-Skills/skills/public-repo-release-review/SKILL.md

public-repo-release-review

Skill2 starsChanged 16 days agoApache-2.0View on GitHub

Review and audit a codebase before releasing or publishing it to public GitHub. Performs deep security checks, secret leak scanning, open-source governance verification (SECURITY.md, COLLABORATORS.md, CITATION.cff, LICENSE, CODE_OF_CONDUCT.md), link integrity checks, and codebase hygiene audits. Use when reviewing a codebase before public release, auditing repository security and governance, or preparing a repository for public GitHub launch.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If governance files are missing or incomplete, run the built-in scaffolding CLI:

    line 59
  2. Distinctive:

    Verify clear one-liner explanation, architecture diagram, installation/quickstart steps, and badges.

    line 84
  3. Distinctive:

    Verify all documented commands execute without syntax or environment errors.

    line 85
  4. Very specific:

    Verify LICENSE matches the SPDX identifier and frontmatter licenses across skills.

    line 87
  5. Very specific:

    If the repository does not accept external pull requests, ensure COLLABORATORS.md explicitly states this upfront to avoid contributor …

    line 89
  6. Distinctive:

    Ensure the terminal reports:

    line 103

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Public Repository Release Review & Pre-Flight Audit

Purpose

Empowers the agent to act as an expert AI engineer, security auditor, and open-source release manager. Conducts a 99.999% rigorous audit before a repository is pushed or made public on GitHub, ensuring zero secret leaks, compliant governance files, intact link integrity, and pristine codebase hygiene.


Procedural Workflow

┌─────────────────────────────────┐
│ 1. Deterministic Security Scan  │ ──> Scan secrets, .env files, high-entropy tokens, .gitignore
└─────────────────────────────────┘
                │
┌─────────────────────────────────┐
│ 2. Governance & Policy Audit    │ ──> Verify SECURITY.md, COLLABORATORS.md, CITATION.cff, etc.
└─────────────────────────────────┘
                │
┌─────────────────────────────────┐
│ 3. Link Integrity & Hygiene     │ ──> Verify relative markdown links, phantom files, dead code
└─────────────────────────────────┘
                │
┌─────────────────────────────────┐
│ 4. Scorecard & Auto-Remediation │ ──> Generate final release audit scorecard & scaffold missing files
└─────────────────────────────────┘

Phase 1: Automated Deterministic Audit

Execute the built-in audit script using run_command:

python <skill_path>/scripts/audit_repo.py --target .

The script automatically verifies:

  1. Secret & Credential Leaks: Scans for AWS tokens, private keys, GitHub tokens, OpenAI/Gemini/Anthropic API keys, high-entropy secrets, and unignored .env* files.
  2. Governance Metadata Compliance: Checks for SECURITY.md, COLLABORATORS.md / CONTRIBUTING.md, CITATION.cff, CITATIONS.md, LICENSE, CODE_OF_CONDUCT.md, SUPPORT.md, and .github/ templates.
  3. Link & Reference Integrity: Scans every Markdown file (*.md) to verify all relative hyperlinks point to physical files.
  4. Codebase Hygiene: Checks for OS junk (.DS_Store, Thumbs.db), untracked large binary blobs (>5MB), and unignored build artifacts.

Phase 2: Missing Governance Scaffolding

If governance files are missing or incomplete, run the built-in scaffolding CLI:

# For solo-maintainer / closed-collaborator repositories:
python <skill_path>/scripts/scaffold_governance.py --target . --collaborators-mode solo --author "Author Name" --email "author@domain.com"

# For open-collaboration community repositories:
python <skill_path>/scripts/scaffold_governance.py --target . --collaborators-mode open --author "Author Name" --email "author@domain.com"

The scaffolding script generates:

  • SECURITY.md: Vulnerability disclosure policy with reporting email and SLA.
  • COLLABORATORS.md: Explicit collaborator guidelines (clearly declaring solo-maintainer or community contributor policy).
  • CITATION.cff & CITATIONS.md: Standard academic and software citation formats (APA, BibTeX, IEEE).
  • CODE_OF_CONDUCT.md: Contributor Covenant v2.1 guidelines.
  • SUPPORT.md: Support channels, discussions, and troubleshooting pointers.
  • .github/: Issue templates (bug_report.yml, feature_request.yml) and pull request template (PULL_REQUEST_TEMPLATE.md).

Phase 3: Semantic Review & Codebase Polish

As an expert AI engineer, conduct a manual semantic pass on critical areas:

  1. Readme Completeness:
    • Verify clear one-liner explanation, architecture diagram, installation/quickstart steps, and badges.
    • Verify all documented commands execute without syntax or environment errors.
  2. License Validity:
    • Verify LICENSE matches the SPDX identifier and frontmatter licenses across skills.
  3. Collaboration Boundary:
    • If the repository does not accept external pull requests, ensure COLLABORATORS.md explicitly states this upfront to avoid contributor confusion.
  4. Attestation & Specs:
    • For skill repositories, ensure every skill directory has attestation.json and evals/test-cases.json.

Phase 4: Final Release Certification

Re-run the audit suite to certify 100% compliance:

python <skill_path>/scripts/audit_repo.py --target . --strict

Ensure the terminal reports:

  • [PASS] 0 Security Leaks Detected
  • [PASS] Governance Files: 100% Present
  • [PASS] Markdown Links: 100% Resolved
  • [PASS] Codebase Hygiene: Clean

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.