prep-repo
FeaturedUse when the user wants to prepare a local project for GitHub or public release. Runs a release-readiness sweep over README structure, bilingual docs, commit hygiene, sensitive-data exposure, broken links, markdown rendering, project layout, tests, CI, Docker, and final cleanup. Fixes issues only inside the target repo and treats secrets/history rewriting as explicit high-risk gates. NOT for publishing without user approval or for private operational runbooks that should not be open-sourced.
Install
Quality Score: 92/100
Skill Content
Details
- Author
- KerberosClaw
- Repository
- KerberosClaw/kc_ai_skills
- Created
- 4 months ago
- Last Updated
- 6 days ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
repo-scan
Use when the user wants to evaluate a GitHub repository before installing, running, forking, or depending on it. Takes a GitHub repo URL, cleans tracking params, shallow-clones to /tmp, inspects dependency/supply-chain risk, static vulnerability patterns, issue-reported security problems, maintainer health, and produces a risk summary. NOT for reviewing the user's own PR diff or for running untrusted code.
readme-steward
当你要为 cc-master 创建、更新、重写、审查或同步 README.md / README_zh.md 时使用;覆盖本仓 README 的产品叙事、英文/中文双语一致性、feature claim 诚实性、用户路径、贡献者路径和视觉/徽章克制。Triggers: README, README_zh, 项目首页, landing page, 文档首页, installation docs, quick start, feature claim, 中英文 README 同步, README review。Do NOT use when 只是改 AGENTS.md / skill body / ADR / feature manual / API 文档本身;那些按对应仓库 skill 或普通文档编辑流程处理。
publish-readiness
Use before making a private repository public, before the first push of a new public repo, or when the user asks "is this safe to publish", "check for leaks", or wants a pre-publication scan. Also use after discovering identifying content already leaked into a public repo's history.