agentleFS
Sign inStart free
roadheroroadhero/claude-code-setup/skills/new-repo/SKILL.md

new-repo

Skill36 starsChanged 2 months agoMITView on GitHub

Scaffold a new repository with the engineering-config hygiene the spine and rules assume. Use when starting a new project, initializing a repo, or "setting up" a web/backend or Android codebase. Lays down .gitignore (with secret patterns), CHANGELOG.md, docs/ stubs (PRD/ROADMAP/ADR), a CI quality-gate + release workflow, and the per-repo CLAUDE.md (§19); for Android, also copies the 7 Android subagents into .claude/agents/. Detects the stack or takes web|android explicitly. Never overwrites existing files.

  • Reads credentials

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. peterpme/skills★ 28same name
    2. 0mlkrizzz655335v/claude-skills-zh★ 2same name
    3. JameMy0001/antigravity-skills-hub★ 1same name
    4. Crawford-Young/claude-config★ 0same name
    5. marslo/skills★ 0same 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.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    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
  1. Very specific:

    Never overwrite: Check each target with test -e.

    line 16
  2. Distinctive:

    One stack per run: Don't lay down both web and Android scaffolding in the same repo unless asked.

    line 17

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

New-repo scaffolder

Lays down the repo hygiene that ~/.claude/CLAUDE.md (§9 stacked-PR, §10 reconciliation, §11 secrets, §6/§7 release/gate in the platform rule) and the agents assume exists — so their references (CHANGELOG.md, docs/REQUIREMENTS.md, the version source, CI) resolve instead of dangling.

When to use

Starting or initializing a new project, or a repo that's missing the standard scaffolding. Ask the user web (TS/JS/Python/Go/…) or android if it isn't obvious from existing files (build.gradle*/*.kt → android; package.json/pyproject.toml → web).

Rules

  • Never overwrite. Check each target with test -e; if it exists, skip it and report "kept existing". The user's files win.
  • One stack per run. Don't lay down both web and Android scaffolding in the same repo unless asked.
  • Fill, don't fabricate. The §19 CLAUDE.md ships with TODO placeholders the user completes — do not invent versions, SDK levels, or compliance scope.
  • Report exactly what was created vs. skipped, as a list.

Procedure

  1. Determine stack (detect or ask). Set STACK=web|android.
  2. From this skill's templates/, copy common/ + <STACK>/ files into the repo (except gitignore-extra.tmpl, which step 3 appends), skipping any that already exist. Template files use a .tmpl suffix to avoid clobbering — strip it on copy (e.g. gitignore.tmpl → .gitignore, <STACK>/CLAUDE.md.tmpl → ./CLAUDE.md). Workflow templates land under .github/workflows/ (gate.yml, release.yml); docs/ stubs under docs/ (REQUIREMENTS.md, ROADMAP.md, and the seed ADR common/0001-foundation.md.tmpl → docs/decisions/0001-foundation.md).
  3. Merge the stack ignores. gitignore-extra.tmpl is not a standalone file — append its contents to the .gitignore created in step 2 (idempotent: skip if those lines are already present). This is the one exception to never-overwrite, since .gitignore is meant to be extended per stack.
  4. For android: also mkdir -p .claude/agents and copy the 7 files from ~/.claude/agents-android/ if present (or tell the user where to get them). For web: no local agents — it inherits the 15 global agents.
  5. git init only if .git is absent. Stage nothing automatically — let the user review.
  6. Print the created/skipped report and the 3 manual follow-ups: fill §19, set the version source, wire branch protection (§7.3).

What gets laid down

common/ (both stacks): .gitignore (secret patterns from §11), CHANGELOG.md (Keep-a-Changelog header), docs/REQUIREMENTS.md, docs/ROADMAP.md, and the seed ADR docs/decisions/0001-foundation.md.

android/: version.properties (versionCode/versionName source of truth), .github/workflows/gate.yml (Spotless/detekt/lint/unit/Roborazzi/compileRelease), .github/workflows/release.yml (tag↔versionName parity → signed build → GitHub Release), CLAUDE.md (§19; the same generic template as web — the Android specifics go into §19 when you fill it in).

web/: .github/workflows/gate.yml (format/lint/typecheck/test/build), .github/workflows/release.yml (tag↔version parity → publish), CLAUDE.md (§19, generic).

Both CLAUDE.md.tmpl files are byte-identical copies of templates/CLAUDE.project.md; the repo's quality gate (CLAUDE.md §19.3) diffs them so they cannot drift.

<STACK>/gitignore-extra.tmpl (both stacks): appended to .gitignore in step 3 — web adds node_modules/, dist/, .next/, coverage/, *.tsbuildinfo; android adds .gradle/, build/, local.properties, *.apk/*.aab, etc.

Secret patterns the .gitignore enforces (§11)

*.env, .env.*, *.pem, *.key, *.keystore, *.jks, **/secrets/, *.p12, google-services.json (android), credentials.json, service-account*.json, *.tfstate*. The user adds project-specific paths.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free