repo-preflight
Skill0 starsChanged 2 months agoMITView on GitHub
Pre-publish health check, retrofit, and audit workflow for GitHub repos. Use when publishing or pushing a project to GitHub, cleaning up a repo before going public, or auditing existing repos for hygiene issues (hardcoded local paths, large files, README structure, community standards).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- TeamSPWK/novatheir own version, first seen Apr 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- TeamSPWK/nova★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Run scripts/scan.sh first — never guess what needs fixing.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
repo-preflight
Overview / 概述
EN: repo-preflight is an agent-executable workflow for the last mile of GitHub publishing. It scans a repository for publish-blocking hygiene issues, produces a structured remediation report, and applies the approved fixes. It covers three flows:
中: repo-preflight 是一套 agent 可执行的 GitHub 发布收尾工作流:扫描仓库中的发布阻断性问题,产出结构化整改报告,并在用户确认后执行整改。共三条流程:
- publish — pre-publish health check and cleanup before pushing to GitHub / 首次推送 GitHub 前的体检与清理. Read
references/sop-publish.md. - retrofit — bring an existing local project up to open-source standards / 把存量本地项目改造到开源标准. Read
references/sop-retrofit.md. - audit — periodic re-check of an already-published repo / 对已发布仓库的定期复查. Read
references/sop-audit.md.
Core discipline / 核心纪律
EN:
- Run
scripts/scan.shfirst — never guess what needs fixing. - Report findings against the checklist in
references/checklist.md; propose fixes, do not apply them silently. - Execute irreversible operations (deleting files, rewriting history, pushing) only after explicit user confirmation.
- Secret scanning is delegated to gitleaks — do not reinvent it.
中:
- 先跑
scripts/scan.sh,绝不靠猜来判断要改什么。 - 对照
references/checklist.md出结构化报告;只提出整改建议,不静默执行。 - 不可逆操作(删文件、改写历史、推送)必须经用户明确确认后再执行。
- 密钥扫描委托给 gitleaks,不重造轮子。
Layout / 目录
references/checklist.md— check item definitions and pass criteria / 体检项定义与通过标准references/sop-*.md— step-by-step SOPs for each flow / 各流程的分步 SOPscripts/scan.sh— mechanizable checks (paths, file sizes, structure) / 可机械化扫描项templates/— README, LICENSE, CONTRIBUTING and other boilerplate / 社区规范件模板
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.

