ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
Initialize GitHub repositories with standard files and configuration.
Install Repo Scaffold
$ npx skills add thatrebeccarae/claude-marketing --skill repo-scaffold -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thatrebeccarae/claude-marketing repo-scaffold --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/repo-scaffold .claude/skills/repo-scaffold && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "repo-scaffold" agent skill from https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/repo-scaffold into .claude/skills/repo-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-scaffold", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/repo-scaffoldType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thatrebeccarae/claude-marketing --skill repo-scaffold -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thatrebeccarae/claude-marketing repo-scaffold --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/repo-scaffold .agents/skills/repo-scaffold && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "repo-scaffold" agent skill from https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/repo-scaffold into .agents/skills/repo-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-scaffold", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thatrebeccarae/claude-marketing --skill repo-scaffold -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thatrebeccarae/claude-marketing repo-scaffold --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/repo-scaffold .cursor/skills/repo-scaffold && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "repo-scaffold" agent skill from https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/repo-scaffold into .cursor/skills/repo-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-scaffold", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thatrebeccarae/claude-marketing.git --path skills/repo-scaffold--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thatrebeccarae/claude-marketing --skill repo-scaffold -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thatrebeccarae/claude-marketing repo-scaffold --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/repo-scaffold .gemini/skills/repo-scaffold && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "repo-scaffold" agent skill from https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/repo-scaffold into .gemini/skills/repo-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-scaffold", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thatrebeccarae/claude-marketing repo-scaffoldInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thatrebeccarae/claude-marketing --skill repo-scaffold -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/repo-scaffold .github/skills/repo-scaffold && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "repo-scaffold" agent skill from https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/repo-scaffold into .github/skills/repo-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-scaffold", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thatrebeccarae/claude-marketing --skill repo-scaffold -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thatrebeccarae/claude-marketing repo-scaffold --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/repo-scaffold .opencode/skills/repo-scaffold && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "repo-scaffold" agent skill from https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/repo-scaffold into .opencode/skills/repo-scaffold/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-scaffold", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
repo-scaffold- GitHub stars
- 161
- Token cost
- ~1.7k tokens
- SKILL.md length
- 763 words
- Files
- 4
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Initialize GitHub repositories with standard files and configuration.
- Works in 7 steps: Validate Repo Path → Scan Existing Files → Detect Project Type → …
- Marketing & SEO work in your project
- SKILL.md covers Install, When to Use, Usage and Procedure, plus 2 more sections
- Calls git and claude
What it does
Repo Scaffold is an agent skill from thatrebeccarae/claude-marketing. Initialize GitHub repositories with standard files and configuration. Generates LICENSE, CONTRIBUTING.md, SECURITY.md, issue/PR templates, CI config, and .gitignore. Detects project type and adapts templates accordingly.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `EXAMPLES.md` and `REFERENCE.md`).
It sits in Marketing & SEO. It works with GitHub, GitHub Actions and Git. The repository describes itself as: A full marketing department for Claude Code. Skill packs for Klaviyo, Shopify, GA4, Looker Studio, paid media, and more. Audit, optimize, and report using natural language. The licence is MIT.
When your agent uses it
- Marketing & SEO work in your project
Example prompts
- “/repo-scaffold”
Requirements
- Python 3
- Node.js
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a8a63ec. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitclaude
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Repo Scaffold loads about 1.7k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 763 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thatrebeccarae/claude-marketing at commit a8a63ec, republished under its MIT licence (© thatrebeccarae). 763 words, ~1,697 tokens.
Download SKILL.mdSave it as
.claude/skills/repo-scaffold/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- repo-scaffold
- description
- Initialize GitHub repositories with standard files and configuration. Generates LICENSE, CONTRIBUTING.md, SECURITY.md, issue/PR templates, CI config, and .gitignore. Detects project type and adapts templates accordingly.
- license
- MIT
- origin
- custom
- author
- Rebecca Rae Barton
- author_url
- https://github.com/thatrebeccarae
- metadata.version
- 1.0.0
- metadata.category
- devops
- metadata.domain
- github
- metadata.updated
- 2026-03-19
- metadata.tested
- 2026-03-19
- metadata.tested_with
- Claude Code v2.1
Repo Scaffold
Initialize GitHub repositories with standard files and configuration. This skill generates LICENSE, CONTRIBUTING.md, SECURITY.md, CODEOWNERS, .gitignore, .editorconfig, YAML-based issue templates, PR template, CI config skeleton, and optional safety files. It detects project type from existing files and adapts all templates accordingly.
Install
claude skill install repo-scaffoldWhen to Use
This skill should be used when:
- Setting up a new GitHub repository from scratch
- Adding missing standard files to an existing repository
- Standardizing repository configuration across projects
- Preparing a private repo for open-source release
Usage
/repo-scaffold [repo-path] [--license MIT|Apache-2.0|ISC] [--public] [--ci github-actions|none]| Flag | Default | Description |
|---|---|---|
repo-path | . (cwd) | Path to the git repository root |
--license | MIT | License type (MIT, Apache-2.0, ISC, GPL-3.0, BSD-2-Clause) |
--public | off | Include .public-repo, .pii-allowlist, .commit-msg-blocklist |
--ci | github-actions | CI provider skeleton (github-actions or none) |
Procedure
Step 1: Validate Repo Path
Confirm the target path is an initialized git repository (contains .git/). If not, halt and inform the user. Never run git init without explicit permission.
Step 2: Scan Existing Files
Inventory the repo root and .github/ directory for any files this skill would generate. Build a conflict list. Never overwrite existing files. If conflicts exist, present them and ask which to skip or replace.
Step 3: Detect Project Type
Identify the primary language and tooling by checking for marker files:
| Marker File | Project Type |
|---|---|
package.json | Node.js / JavaScript / TypeScript |
pyproject.toml, setup.py, requirements.txt | Python |
Cargo.toml | Rust |
go.mod | Go |
| Multiple markers | Multi-language |
| None of the above | Generic |
If multiple markers are found, treat as multi-language and combine relevant patterns.
Step 4: Generate Files
Generate each file with language-appropriate content. Refer to REFERENCE.md for templates, patterns, and format specifications.
4a. LICENSE
Prompt the user for license choice if --license was not provided. Default to MIT. Insert the current year and the repo owner's name (from git config user.name or ask). See REFERENCE.md license comparison table for guidance.
4b. .gitignore
Generate language-appropriate ignore patterns based on the detected project type. Combine patterns for multi-language repos. Always include OS-level ignores (.DS_Store, Thumbs.db) and editor ignores (.vscode/, .idea/).
4c. CONTRIBUTING.md
Generate a fork-branch-PR contribution guide. Include:
- Fork and clone instructions
- Branch naming conventions (
feat/,fix/,docs/) - Code style notes (link to linter config if detected)
- Commit message format
- PR checklist
4d. SECURITY.md
Generate a security policy with:
- Supported versions table (populate from package version if detectable)
- Vulnerability reporting instructions (email-based, not public issues)
- Response timeline expectations
4e. CODEOWNERS
Scan the top-level directory structure and generate a CODEOWNERS file. Map directories to the repo owner by default. Add comments explaining how to customize.
4f. .editorconfig
Generate settings appropriate to the detected project type:
- Indent style and size
- End-of-line character
- Trim trailing whitespace
- Insert final newline
- Charset (utf-8)
4g. .github/ISSUE_TEMPLATE/bug-report.yml
Generate a YAML form-based bug report template with fields: description, steps to reproduce, expected behavior, actual behavior, environment, and optional screenshots. See REFERENCE.md for YAML form spec.
Show full SKILL.md (303 more words)Show less
4h. .github/ISSUE_TEMPLATE/feature-request.yml
Generate a YAML form-based feature request template with fields: problem statement, proposed solution, alternatives considered, and additional context.
4i. .github/pull_request_template.md
Generate a PR template with sections: summary of changes, type of change (checkboxes), testing performed, and checklist.
4j. .github/workflows/ci.yml
Generate a CI skeleton for GitHub Actions (unless --ci none). Include:
- Trigger on push to main and pull requests
- Language-appropriate setup step
- Lint step (ESLint, ruff, clippy, golangci-lint)
- Test step (language-appropriate test runner)
- Placeholder comments for additional steps
4k. Optional: Safety Files (when --public)
When --public is passed, also generate:
.public-repo— Empty marker file indicating the repo is public.pii-allowlist— One regex per line; starts with a comment header explaining usage.commit-msg-blocklist— One term per line; starts with a comment header and common defaults
Step 5: Present Plan
Before writing any files, present the full list of files to be created with a one-line description of each. Show which files were skipped due to conflicts. Ask the user to confirm before proceeding.
Step 6: Write Files
Write all confirmed files. Report each file as it is written.
Step 7: Summary
Print a summary table:
- Files created (with paths)
- Files skipped (with reason)
- Suggested next steps (e.g., review CODEOWNERS, customize CONTRIBUTING.md, add secrets to CI)
Key Principles
- Never overwrite existing files. Always scan first, flag conflicts, and ask.
- Always ask before writing. Present the plan and get explicit confirmation.
- Language-appropriate defaults. Detect the project type and tailor every template.
- Minimal but complete. Generate the standard set every well-maintained repo needs, nothing more.
- Composable. Each file stands alone. Re-run the skill later to add missing files without disrupting existing ones.
References
- REFERENCE.md — License comparison, .gitignore patterns, YAML template spec, CI skeletons, CODEOWNERS syntax, .editorconfig settings, SECURITY.md and CONTRIBUTING.md templates
- EXAMPLES.md — Worked examples for Node.js, Python, and public repo scaffolding
© thatrebeccarae, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files in skills/repo-scaffold of thatrebeccarae/claude-marketing.
- SKILL.md
- EXAMPLES.md
- LICENSE
- REFERENCE.md
Open the folder on GitHubat commit a8a63ec
Compare with similar skills
Repo Scaffold next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Repo Scaffold this skillthatrebeccarae/claude-marketing | 161 | — | ~1.7k | Automated safety check: Pass | MIT | |
| ZCF Release AutomationUfoMiao/zcf | 6.1k | — | ~3.4k | Automated safety check: Pass | MIT | |
| npm Package Publisherklaudworks/universal-skills | 181 | — | ~923 | Automated safety check: Pass | MIT | |
| Kt Search Releasejillesvangurp/kt-search | 155 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Git GitHub Opsc5inco/compose-pokedexer | 143 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Push and PyPI Releaseliaohch3/claude-tap | 3.3k | — | ~509 | Automated safety check: Pass | MIT |
Similar skills
npm Package Publisher
klaudworks/universal-skills
Releases an npm package by committing changes, bumping the version with npm version, pushing the tag and checking the GitHub Actions publish.
Kt Search Release
jillesvangurp/kt-search
A skill your agent uses when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed…
Git GitHub Ops
c5inco/compose-pokedexer
Handles Pokedexer Git and GitHub workflows: inspect changes, prepare commit messages, manage branches and pushes, and create or update issues and pull requests with safe file-based inputs.
Push and PyPI Release
liaohch3/claude-tap
Pushes the current work to GitHub and, when pending commits change code, bumps the version in pyproject.toml so CI publishes a new PyPI release.
PR Create
posit-dev/skills
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes.
More from thatrebeccarae/claude-marketing
All 55 skills in this repoGoogle Analytics
thatrebeccarae/claude-marketing
Analyze Google Analytics data, review website performance metrics, identify traffic patterns, and suggest data-driven improvements.
Content Creator
thatrebeccarae/claude-marketing
Comprehensive content marketing toolkit with brand voice analysis, SEO optimization scripts, content frameworks, social media strategy, and content calendar planning.
Klaviyo Analyst
thatrebeccarae/claude-marketing
Klaviyo marketing operations and analyst expertise. An agent skill from thatrebeccarae/claude-marketing.
Klaviyo Developer
thatrebeccarae/claude-marketing
Klaviyo API and developer integration expertise. An agent skill from thatrebeccarae/claude-marketing.
Looker Studio
thatrebeccarae/claude-marketing
Looker Studio (formerly Google Data Studio) expertise. An agent skill from thatrebeccarae/claude-marketing.
Shopify
thatrebeccarae/claude-marketing
Shopify e-commerce platform marketing expertise. An agent skill from thatrebeccarae/claude-marketing.
Related
Works with
Categories
Questions about Repo Scaffold
What does Repo Scaffold do?
Initialize GitHub repositories with standard files and configuration. Repo Scaffold is an agent skill from thatrebeccarae/claude-marketing. Initialize GitHub repositories with standard files and configuration.
When should I use Repo Scaffold?
Repo Scaffold fits situations like: marketing & SEO work in your project.
How do I install Repo Scaffold in Claude Code?
Run `npx skills add thatrebeccarae/claude-marketing --skill repo-scaffold -a claude-code`. Or copy the skill folder (skills/repo-scaffold in thatrebeccarae/claude-marketing) into .claude/skills/repo-scaffold in your project. Claude Code loads it when a task matches its description.
How do I install Repo Scaffold in Codex?
Run `npx skills add thatrebeccarae/claude-marketing --skill repo-scaffold -a codex`. Or copy the skill folder (skills/repo-scaffold in thatrebeccarae/claude-marketing) into .agents/skills/repo-scaffold in your project. Codex loads it when a task matches its description.
Can I use Repo Scaffold in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thatrebeccarae/claude-marketing --skill repo-scaffold -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/repo-scaffold, .gemini/skills/repo-scaffold, .github/skills/repo-scaffold and .opencode/skills/repo-scaffold in your project.
What does Repo Scaffold need to run?
Going by SKILL.md and its folder, Repo Scaffold needs the command-line tools its instructions call (git and claude). Our summary lists: Python 3; Node.js.
Does Repo Scaffold access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Repo Scaffold safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Repo Scaffold use?
Repo Scaffold is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Repo Scaffold use?
About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Repo Scaffold?
Skills that share tags, products or a category with Repo Scaffold: ZCF Release Automation (UfoMiao/zcf, 6.1k stars), npm Package Publisher (klaudworks/universal-skills, 181 stars), Kt Search Release (jillesvangurp/kt-search, 155 stars) and Git GitHub Ops (c5inco/compose-pokedexer, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Repo Scaffold?
thatrebeccarae (a GitHub user) maintains it in thatrebeccarae/claude-marketing, which has 161 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on May 14, 2026.
Source: thatrebeccarae/claude-marketing on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.