A repository cleanup and setup aid for preparing a code project for sharing. It creates common files such as a README, license, environment-variable template, and rules for files Git should ignore.

Use it when starting a repository, checking an existing one, or preparing a project for public release. It checks for missing project files and committed secrets, then creates or updates the needed files.

It helps prevent secrets, temporary files, and machine-specific files from being committed, while making the project easier for others to understand and use.

repo-polish — Skill for Claude Code by Sagargupta16

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Sagargupta16/claude-skills --skill repo-polish

Clone the repo

git clone --depth 1 https://github.com/Sagargupta16/claude-skills

Made for: Claude Code.

Or install repo-polish, the plugin that ships this one along with the rest of its 1 skill, 1 command, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sagargupta16/claude-skills/repo-polish/github.svg)](https://agentmods.dev/skills/sagargupta16/claude-skills/repo-polish)

Your own site

<a href="https://agentmods.dev/skills/sagargupta16/claude-skills/repo-polish"><img src="https://agentmods.dev/badge/skills/sagargupta16/claude-skills/repo-polish/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sagargupta16/claude-skills/repo-polish"><img src="https://agentmods.dev/badge/skills/sagargupta16/claude-skills/repo-polish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,616 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00046	$0.01616
Opus 5	$0.00023	$0.00808
Sonnet 5	$0.00009	$0.00323
Haiku 4.5	$0.00005	$0.00162

Measured 12d ago against content hash 88c8419178a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

repo-polish scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/repo-polish/skills/repo-polish/SKILL.md · 263 lines

How it starts

The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Polish

Audit Checklist

Item	Required	Check
`.gitignore`	Yes	Covers OS files, editor files, language artifacts, .env, secrets
`.env.example`	If .env used	Documents all env vars with placeholder values
`README.md`	Yes	Project name, description, setup, usage, tech stack
`LICENSE`	Yes	MIT for personal, match upstream for forks
No committed secrets	Critical	No .env, credentials, API keys in git history

Workflow

Sync first: git pull before making changes (skip for forks)
Detect: Identify project type from config files
Audit: Check what exists and what's missing
Fix: Create/update files using templates below
Verify: Search for committed secrets
Commit: chore: add missing repo hygiene files

.gitignore Templates

Node.js / React / Next.js

node_modules/
dist/
build/
.next/
.env
.env.local
.env.*.local
*.log
npm-debug.log*
.DS_Store
Thumbs.db
.vscode/
.idea/
coverage/

Python / FastAPI / ML

__pycache__/
*.py[cod]
*$py.class
*.so
venv/
.venv/
.env
*.egg-info/
dist/
build/
.pytest_cache/
.coverage
htmlcov/
*.h5
*.pkl
*.model
*.weights
.ipynb_checkpoints/
.DS_Store
Thumbs.db
.vscode/
.idea/

Go

bin/
vendor/
*.exe
*.test
*.out
.env
.DS_Store
Thumbs.db
.vscode/
.idea/

Rust

target/
Cargo.lock
*.pdb
.env
.DS_Store
Thumbs.db
.vscode/
.idea/

Unity / C#

[Ll]ibrary/
[Tt]emp/
[Oo]bj/
[Bb]uild/
[Bb]uilds/
[Ll]ogs/
[Uu]ser[Ss]ettings/
*.csproj
*.sln
*.suo
*.user
*.pdb
.DS_Store
Thumbs.db

.env.example Generation

Search for env var usage in the codebase:
- Node.js: process.env.VAR_NAME
- Python: os.environ["VAR"], os.getenv("VAR"), dotenv
- Go: os.Getenv("VAR")
- Config files: YAML, JSON, TOML loaders

Write placeholders - never real values:

# Database
DATABASE_URL=postgresql://localhost:5432/dbname

# Authentication
JWT_SECRET=your-secret-key-here

# External APIs
API_KEY=your-api-key-here

Read the full file on GitHub · 263 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 263 lines · 46 tokens per session scan A 88c8419178a4

Subscribe to this mod's changes

repo-polish is a skill published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 1,616 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Git and workflow Security ai-agents claude developer-tools marketplace plugins

release

This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and optionally publish to npm. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate".

NikiforovAll/claude-code-marketplace · 60 tokens

cut-release

Prepare and publish an explicitly requested Foundry plugin-edition release using its actual platform branch, version owner and catalog. Includes coordinated README and verification gates; never an automatic release trigger.

V-Songbird/foundry · 39 tokens

team-workspace

Set up or work with a git-backed team workspace for co-owned artifacts — charters, strategy docs, decision records — separate from private reflections. Triggers: "share our team charter with the team", "set up a shared haku workspace", "put our strategy doc in the team repo", "how do teams use haku together".…

shrwnsan/vibekit-claude-plugins · 0 tokens

crafting-commits

Generates git commit messages following conventional commit standards with collaborative attribution. Use when user requests commit message creation, drafting, or help with formatting.

shrwnsan/vibekit-claude-plugins · 34 tokens

branch-hygiene

Classify and clean up merged, stale, and orphaned git branches and worktrees. Detects squash-merges that git branch --merged cannot see, stale worktrees, and remote-gone branches. Use when user asks to clean up branches, prune worktrees, tidy the repo, or perform git housekeeping.

shrwnsan/vibekit-claude-plugins · 68 tokens

changelog-summarizing

Use this skill when the user asks to summarize, recap, or post about repository changes in the Shopware AI Coding Tools marketplace since a given date — phrases like "write a changelog post for Discord", "recap this week's commits for Slack", "summarize what shipped since 2026-04-01", "draft a release announcement".…

shopwareLabs/ai-coding-tools · 106 tokens