skills/init-repo/SKILL.md
Initialize a git repository in the current (empty) folder with a curated .gitignore. Creates project-specific ignore entries plus community gitignore content for the specified technology types. Use when starting a brand-new project from scratch.
npx skillsauth add adeshmukh/claude-skills init-repoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Initialize a git repository with a curated .gitignore file.
$ARGUMENTS — comma-separated list of gitignore types (e.g. python,node,macos).
These map to entries on the gitignore.io API.
If no arguments are provided, ask the user what types they need.
.git/ directory. If it does, stop and inform the user that a git repo already exists.Run:
git init
Create a .gitignore file with the following structure:
Project-specific entries (always included at the top):
# Project-specific
.worktree/
worktree/
.local/
Community entries (fetched from gitignore.io):
Fetch content from:
https://www.toptal.com/developers/gitignore/api/<TYPES>
Where <TYPES> is the value of $ARGUMENTS (e.g. python,node,macos).
Append the fetched content below the project-specific entries, separated by a blank line.
If the fetch fails, warn the user and write only the project-specific entries. Do not fail the entire operation.
git add .gitignore
git commit -m "Initial commit with .gitignore"
Tell the user:
git remote add origin <url>)development
Set up a modern Python project using uv (package manager) and ruff (linter/formatter). Initializes pyproject.toml with sensible ruff rules, creates a virtual environment, and optionally migrates an existing requirements.txt. Use when starting a new Python project.
tools
Generate a context-sensitive, self-documenting Makefile by analyzing the current project. Detects languages, frameworks, and tools to select appropriate targets (build, test, lint, deploy, etc.). Presents proposed targets for approval before writing. Use on any project that would benefit from a standardized Makefile.
testing
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".
testing
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).