claude-init

Name: claude-init
Availability: InStock
Author: JYbill

Consolidate repository guidance into a single CLAUDE.md for Claude Code.

1|Updated Mar 14, 2025

Search Tags:#claude-code #claude-md #repository-guidance #team-governance #documentation-consolidation #guidelines-migration

Ready to run

npx skills add https://github.com/JYbill/bullboard-nestjs --skill claude-init

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: claude-init
Source: https://github.com/JYbill/bullboard-nestjs/tree/main/.claude/skills/claude-init
Command: npx skills add https://github.com/JYbill/bullboard-nestjs --skill claude-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams create, update, or converge a repository-level CLAUDE.md for Claude Code, preserving only high-signal collaboration constraints, non-obvious rules, tooling caveats, and project-specific boundaries, while consolidating guidance from AGENTS.md or legacy Cursor/Copilot prompts.

Core Features & Use Cases

Initialize or migrate CLAUDE.md for Claude Code repositories.
Convert existing Cursor, Copilot, or AGENTS.md guidance into Claude Code-ready rules.
Prune redundant or outdated sections to maintain a concise, high-signal document.
Ensure governance boundaries are explicit and actionable for developers and reviewers.

Quick Start

Convert your repository's current collaboration guidance into a Claude Code CLAUDE.md and prune it to essential guardrails and project-specific rules.

Frequently Asked Questions about claude-init

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

FAQPage Schema

How do I migrate AGENTS.md to CLAUDE.md for Claude Code?▼

Migrating AGENTS.md to CLAUDE.md consolidates existing repository guidance into a single, high-signal document. The process converts legacy collaboration constraints into Claude Code-ready rules while pruning redundant sections to maintain actionable governance boundaries.

What is the best way to consolidate Cursor and Copilot instructions into a CLAUDE.md file?▼

Consolidating Cursor and Copilot instructions into a CLAUDE.md file converts legacy prompts into project-specific boundaries. This convergence preserves non-obvious rules and tooling caveats while ensuring documentation remains concise and actionable for Claude Code repositories.

Why does my repository CLAUDE.md contain outdated or redundant governance rules?▼

Repository CLAUDE.md files accumulate outdated governance rules when legacy content is not pruned. Consolidating and converging guidance removes redundant sections, preserving only high-signal collaboration constraints and project-specific rules to maintain a concise document.

Can I initialize a CLAUDE.md file without existing AGENTS.md or Cursor instructions?▼

Initializing a CLAUDE.md file without existing AGENTS.md or Cursor instructions creates project-specific boundaries from scratch. The convergence process establishes actionable governance, guardrails, and tooling caveats tailored to your codebase requirements for Claude Code.

Does CLAUDE.md require explicit governance boundaries for team reviewers?▼

CLAUDE.md requires explicit governance boundaries for team reviewers to ensure project-specific rules are actionable. Consolidating repository-level guidance satisfies governance requirements by preserving high-signal constraints and non-obvious rules within the converged document.

When do I need to converge multiple CLAUDE.md files across a codebase?▼

Converging multiple CLAUDE.md files across a codebase is needed when repository guidance becomes fragmented. This consolidation prunes outdated sections and merges legacy content into a single, high-signal document with explicit guardrails for Claude Code.