repo-polishlisted

# repo-polish Prepare a personal project for world-class open-source publication on GitHub under **TamirCohen28**. ## Reference standard Model every decision on `/Users/tamircohen/Projects/production-master`, which has: - Hero `README.md` with badges, feature highlights, prerequisites, quick start - `docs/user/` — concepts, quick-start, troubleshooting, guides, reference - `docs/engineering/` — architecture, build-and-release, decisions (ADRs), guides, reference - `docs/CHANGELOG.md`, `docs/CONTRIBUTING.md` - `.github/` — `ci.yml`, `release.yml`, `dependabot.yml`, PR template, issue templates - `CLAUDE.md` — Claude Code guidance - `.claude/rules/` — governance rules - `assets/` — banner and visual assets - `CODEOWNERS`, `Makefile`, `LICENSE` ## Required execution flow ### Step 0 — Resolve project directory Parse `$ARGUMENTS`. If it's a valid directory path, use it. If empty or not a directory: ``` Ask: "Which project directory should I polish? (provide absolute path)" ``` Stop until you have a real directory. Set `PROJECT_DIR` to the absolute canonical path: ```bash PROJECT_DIR="$(cd "$ARGUMENTS" && pwd)" ``` ### Step 1 — Survey the project Read enough to understand what was built: ```bash # Structure overview find "$PROJECT_DIR" -maxdepth 3 -not -path '*/node_modules/*' -not -path '*/.git/*' \ -not -path '*/dist/*' -not -path '*/build/*' -not -path '*/__pycache__/*' | sort # Key files for f in README.md package.json pyproject.toml go.mod Cargo.toml; do [[ -f "$