doc-readme
SKILL.md
README
Create, update, and validate README.md files with auto-detection of project type and install commands.
Workflow
Creating New README
For projects without README.md:
scripts/init_readme.py [--path <project>] [--force]
This will:
- Detect project type from package files
- Extract metadata (name, description, license)
- Extract install/test commands from package manager
- Generate structured README from template
Updating Existing README
For projects with README.md:
scripts/update_readme.py [--path <project>]
This will:
- Parse existing README sections
- Refresh content within
<auto>tags - Preserve all user-written content outside tags
Validating README
Check README for staleness:
scripts/validate_readme.py [--path <project>] [--fix]
This will:
- Check required sections are present
- Verify install commands are current
- Check referenced files exist
- Apply fixes if
--fixprovided
Project Type Detection
| Files Present | Type | Install Command |
|---|---|---|
package.json + pnpm-lock.yaml |
nodejs | pnpm install |
package.json + yarn.lock |
nodejs | yarn |
package.json + bun.lockb |
nodejs | bun install |
package.json |
nodejs | npm install |
pyproject.toml (poetry) |
python | poetry install |
pyproject.toml (uv) |
python | uv sync |
pyproject.toml |
python | pip install -e . |
Cargo.toml |
rust | cargo build |
go.mod |
go | go build ./... |
Auto-Generated Sections
Content within <auto> tags is refreshed on update:
## Installation
<auto>
npm install my-package
</auto>
Your custom notes here are preserved.
Auto-updatable content:
- Installation commands
- Test commands
- Prerequisites/versions
Template
See references/template.md for the full README template structure.
Weekly Installs
1
Repository
molechowski/cla…e-skillsFirst Seen
9 days ago
Security Audits
Installed on
amp1
cline1
opencode1
cursor1
kimi-cli1
codex1