Sponsor Suno AI Music arrow_forward
Slash Command

Project Init

Initialize a new project with git setup, CI/CD workflows, pre-commit hooks, Makefiles, and language-specific tooling.

Type
Slash Command
GitHub stars
339
License
MIT
Repo last updated
Sep 24, 2026

What Project Init is

Project Init is a slash command published in the athola/claude-night-market repository on GitHub, which has about 339 stars. The repository describes itself as: “23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context optimization, research, and multi-LLM delegation. 186 skills, 128 commands, 54 agents.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Project Init gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Project Init

Claude Code

  1. Download project-init.md from the repository.
  2. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
  3. Run it by typing / followed by its name.

Claude Cowork

  1. Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
  2. In Customize → Skills, click +, then upload the ZIP.
  3. Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/attune/commands/project-init.md, shared under the repository's MIT license. Read the full file on GitHub.

Initialize or update projects with complete development infrastructure and standard tooling.

When To Use

Use this command when you need to:

  • Start a new project from scratch
  • Set up development infrastructure (git, Makefile, CI/CD)
  • Bootstrap project with language-specific tooling
  • Initialize empty repository with standards
  • Create project structure and configurations

When NOT To Use

Avoid this command if:

  • Project already initialized and configured
  • Only need specific component updates (use /attune:upgrade-project)
  • Need architecture selection first (use /attune:arch-init)
  • Modifying established project structure

Usage

# Interactive mode (recommended)
/attune:project-init

# Specify language
/attune:project-init --lang python

# Full specification
/attune:project-init --lang python --name my-project --author "Your Name"

What This Command Does

  1. Detects or accepts language specification (Python, Rust, TypeScript)
  2. Initializes git repository (if not already initialized)
  3. Creates or updates configuration files:
  • .gitignore - Language-specific ignores
  • Makefile - Development automation
  • .pre-commit-config.yaml - Code quality hooks
  • pyproject.toml / Cargo.toml / package.json - Dependency management
  1. Sets up or updates GitHub workflows:
  • Test workflow
  • Lint workflow
  • Type check workflow
  1. Creates project structure (if not present):
  • src/ directory with initial module
  • tests/ directory
  • README.md

Note: For existing projects, init will detect present configurations and offer to update them to current standards. Use --force to overwrite without prompting, or the interactive mode for selective updates.

Workflow

# 1. Invoke skill to guide initialization
Skill(attune:project-init)

# 2. Gather project metadata
#    - Project name (default: directory name)
#    - Language (detect or ask)
#    - Author name
#    - Python version (if Python)
#    - License type

# 3. Run initialization script
python3 plugins/attune/scripts/attune_init.py \
  --lang python \
  --name "my-awesome-project" \
  --author "Your Name" \
  --path .

# 4. Validate setup
…

Arguments

  • --lang - Project language (python, rust, typescript)
  • --name - Project name (default: directory name)
  • --author - Author name
  • --email - Author email
  • --python-version - Python version (default: 3.10)
  • --description - Project description
  • --path - Project path (default: current directory)
  • --force - Overwrite existing files without prompting
  • --no-git - Skip git initialization

Interactive Mode

When no arguments provided, the skill guides you through:

  1. Language detection: Auto-detect or let you choose
  2. Project metadata: Name, author, description
  3. Feature selection: Which components to initialize
  4. Confirmation: Review before applying changes
  5. Execution: Run initialization with your choices

Safety Features

  • Non-destructive: Prompts before overwriting existing files
  • Validation: Checks for conflicts before copying templates
  • Dry-run option: Preview changes without applying (#97)
  • Backup option: Create backups of overwritten files (#98)

Examples

Example 1: New Python CLI Project

/attune:project-init --lang python --name awesome-cli --description "An awesome CLI tool"

Creates:

awesome-cli/
├── .git/
├── .gitignore
├── .pre-commit-config.yaml
├── pyproject.toml
├── Makefile
├── README.md
├── src/
│   └── awesome_cli/
│       └── __init__.py
├── tests/
│   └── __init__.py
└── .github/
    └── workflows/
        ├── test.yml
        ├── lint.yml
        └── typecheck.yml

Example 2: Initialize in Existing Project

cd my-existing-project
/attune:project-init --lang python

Prompts:

File exists: pyproject.toml. Overwrite? [y/N]: n
⊘ Skipped: pyproject.toml
File exists: Makefile. Overwrite? [y/N]: y
✓ Created: Makefile
...

Example 3: Force Overwrite All Files

/attune:project-init --lang python --force

Overwrites all existing files without prompting.

Post-Initialization Steps

After initialization, run:

# Install dependencies and set up pre-commit hooks
make dev-setup

# Verify installation
make test

# See all available targets
make help

Troubleshooting

Git not initialized:

# Initialize manually
git init
/attune:project-init --lang python

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Project Init?

Project Init is a slash command for Claude Code and Claude Cowork from the athola/claude-night-market repository on GitHub. Initialize a new project with git setup, CI/CD workflows, pre-commit hooks, Makefiles, and language-specific tooling.

How do I install Project Init in Claude Code?

Download project-init.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Project Init in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Project Init safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.