{
  "markdown": "# public-repo-readiness\n\nA Claude Code skill that audits your codebase before you open-source it.\n\nIt checks for secrets, PII, internal infrastructure references, and licensing issues — then writes a remediation plan and walks you through fixing everything.\n\n## Install\n\n```bash\nmkdir -p ~/.claude/skills/public-repo-readiness && \\\n  curl -o ~/.claude/skills/public-repo-readiness/SKILL.md \\\n  https://raw.githubusercontent.com/dlewis7444/public-repo-readiness/main/skills/public-repo-readiness/SKILL.md\n```\n\n## Usage\n\nIn Claude Code, say:\n\n> \"make this repo public ready\"\n\nor any similar phrasing: *\"publicize the repo\"*, *\"public-ready check\"*, *\"genericize the repo\"*.\n\n## What it checks\n\n- **Secrets & credentials** — API keys, tokens, private keys, DB connection strings; checks both working tree and full git history\n- **PII** — email addresses in code and commit history\n- **Internal infrastructure** — hostnames, IPs, internal domain names, private Docker registries; auto-detected from your local environment\n- **Licensing** — missing LICENSE file, copyleft dependencies that may restrict your chosen license\n\n## Walkthrough\n\nHere's what a typical run looks like:\n\n```\nYou: make this repo public ready\n\nClaude: I'll run a public repo readiness audit. First, let me check for recommended\n        scanning tools...\n\n        The following tools are missing and recommended for a thorough audit:\n\n          [ ] gitleaks     — fast secret scanner, checks full git history\n          [ ] trufflehog   — deep secret scanner, verifies if credentials are still active\n\n        Should I install any of these? (yes to all / pick specific ones / skip)\n\nYou: yes to all\n\nClaude: Installing gitleaks and trufflehog...\n        [installs tools]\n\n        Running auto-detection of internal hostnames, subnets, and domains from\n        your local environment...\n\n        Detected:\n          Hostnames: webserver1, db-primary, ci-runner\n          Subnets:   10.0.0.0/8, 192.168.1.0/24\n          Domains:   home.lab, internal\n\n        Starting scan...\n\n        [scans git history, working tree, licenses]\n\n        Scan complete. Before I write the remediation plan, I need a few decisions:\n\n        1. LICENSE: No LICENSE file found. Which license do you want?\n           (MIT / Apache 2.0 / GPL-3.0 / other)\n\n        2. GIT HISTORY REWRITE: 1 secret found in committed history.\n           Proceed with history rewrite plan? (yes / no / I'll handle manually)\n\n        3. SCOPE: These are borderline — include in remediation or leave?\n           - README.md:14 — mentions \"db-primary\" which matches your internal hostname\n\nYou: MIT, yes to history rewrite, include the README mention\n\nClaude: Writing remediation plan to ./public-repo-remediation-plan.md...\n\n        Plan saved. Use /clear then tell me to implement the plan using the\n        executing-plans skill to execute it in a fresh context.\n```\n\n## Requirements\n\n- [Claude Code](https://claude.ai/code)\n- Optional (skill will prompt to install): [`gitleaks`](https://github.com/gitleaks/gitleaks), [`trufflehog`](https://github.com/trufflesecurity/trufflehog)\n\n## Contributing\n\nIssues and PRs welcome. The skill logic lives entirely in `skills/public-repo-readiness/SKILL.md`.\n",
  "bytes": 3222,
  "sha": "93a52f49f881b5f5f72cb8aa1a6b9752cf6c966770c6de37a6c159a45c1a4741",
  "repo_slug": "dlewis7444/public-repo-readiness",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_dlewis7444_public_repo_readiness_public__5e4bd253/readme"
}