pj-init

Initialize CLAUDE.md for multi-repo workspaces under ~/pj/{project}/.

9|Updated Jan 31, 2017
One-click install
npx skills add https://github.com/ssiumha/dots --skill pj-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pj-init
Source: https://github.com/ssiumha/dots/tree/main/prompts/skills/pj-init
Command: npx skills add https://github.com/ssiumha/dots --skill pj-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

In a multi-repo workspace under ~/pj/{project}/, CLAUDE.md needs a consistent starter. This Skill initializes CLAUDE.md for the entire workspace and sets up living-docs integration, enabling unified governance across repositories.

Core Features & Use Cases

  • Discover all sub-repos under the workspace and infer roles (backend, frontend, etc.)
  • Inspect README/package.json in each repo to tailor CLAUDE.md templates
  • Create CLAUDE.md from a central template (templates/workspace.md)
  • Integrate with living-docs at ~/docs/pj--{project}/
  • Use cases: new workspace onboarding, existing workspace updates, repository augmentation

Quick Start

Run in the top-level workspace (e.g., ~/pj/myproject/):

  • Execute the skill to generate CLAUDE.md and proposed living-docs layout
  • Answer prompts to customize project descriptions and relationships

Frequently Asked Questions about pj-init

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

FAQPage Schema
How do I initialize CLAUDE.md for a multi-repo workspace?

Initialize CLAUDE.md by running the skill in your top-level workspace directory (~/pj/{project}/). It discovers all git repositories, collects metadata like tech stack and package managers, prompts you for project description and inter-repo relationships, then generates CLAUDE.md from a workspace template and sets up living-docs integration at ~/docs/pj--{project}/.

What's the difference between a multi-repo workspace and a monorepo for CLAUDE.md setup?

A multi-repo workspace organizes independent git repositories under ~/pj/{project}/ as separate projects with distinct remotes, while a monorepo is a single repository with multiple packages. This skill applies to multi-repo workspaces, not monorepos, and generates unified CLAUDE.md governance across independently versioned repositories.

Can I update an existing workspace's CLAUDE.md without starting over?

Yes. The skill supports existing workspace updates by re-discovering repositories, re-collecting per-repo details, and regenerating CLAUDE.md while respecting your previous customizations through prompts for project description and inter-repo relations.

What information does the skill collect from each repository?

The skill inspects each repository's README and package.json to infer technology stack, identifies package managers and build commands, detects exposed ports, discovers git remotes, and collects per-repo metadata to tailor CLAUDE.md templates for accurate workspace documentation.

How does CLAUDE.md integrate with living-docs in a multi-repo workspace?

The skill generates CLAUDE.md at the workspace root and creates a proposed living-docs directory structure at ~/docs/pj--{project}/, linking workspace governance documentation to per-repository context and enabling centralized reference management across your git repositories.