init-claude-setup

Initializes Claude project-level settings and updates .gitignore entries automatically.

31|6|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/nickmaglowsch/claude-setup --skill init-claude-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-claude-setup
Source: https://github.com/nickmaglowsch/claude-setup/tree/main/.claude/skills/init-claude-setup
Command: npx skills add https://github.com/nickmaglowsch/claude-setup --skill init-claude-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize project-level Claude configuration by updating repository-level ignore and settings so teams can standardize environment without duplicating agent/skill files. If full local Claude install is already present, no action is needed.

Core Features & Use Cases

  • Detects whether a full local Claude install exists and skips unnecessary changes.
  • Adds missing .gitignore entries under a dedicated .claude section to hide sensitive and Claude-specific folders.
  • Creates .claude/settings.local.json when missing to define per-project permissions safely.
  • Produces a concise summary of actions taken to aid auditing and reproducibility.

Quick Start

Run the setup script to initialize project-level Claude configuration in the current repository.

Frequently Asked Questions about init-claude-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I initialize Claude configuration for an existing repository?

To initialize Claude configuration, the setup automatically updates .gitignore and creates .claude/settings.local.json. This standardizes your project environment by safely adding required ignore rules and per-project permission files without duplicating agent files.

What happens if I already have a full local Claude installation in my project?

If a full local Claude installation is already detected in your repository, the setup script skips unnecessary changes and takes no action. This ensures idempotent updates and prevents destructive changes to your existing environment configuration.

How does adding .claude to .gitignore protect sensitive project folders?

Adding .claude entries to .gitignore hides sensitive and Claude-specific folders from version control. The setup script applies these ignore rules under a dedicated section, ensuring local settings and environment configurations are not exposed in shared repositories.

Can I use this automated project setup to safely generate settings.local.json?

Yes, you can use this automated project setup to safely generate .claude/settings.local.json. It creates the file when missing to define per-project permissions safely, ensuring no destructive changes occur to existing configuration files.

What are the limitations of automating Claude project setup with this script?

The script's limitations include skipping initialization entirely when a full local Claude install is detected, and only creating .claude/settings.local.json when the file is missing. It enforces idempotent updates, meaning it will not overwrite existing configurations.