README Updater Skill

Keep your README current with project changes.

When I Activate

• ✅ New features added
• ✅ Project structure changes
• ✅ Dependencies added/removed
• ✅ Setup instructions change
• ✅ User mentions README or documentation
• ✅ Configuration files modified

What I Update

README Sections

Installation:

• New dependencies
• Setup steps
• Prerequisites
• Environment variables

Features:

• New capabilities
• Functionality changes
• Feature deprecation

Usage:

• API changes
• New examples
• Updated screenshots

Configuration:

• New options
• Environment variables
• Config file changes

Examples

New Feature Addition

bash
1# You add authentication:
2git diff
3# + auth.service.ts
4# + login.component.tsx
5# + JWT middleware
6
7# I suggest README update:
8## Features
9- ✨ User authentication with JWT  # NEW
10- 🔐 Role-based access control    # NEW
11- User management
12- Dashboard

New Dependency

bash
1# You add: npm install stripe
2
3# I suggest:
4## Installation
5
6```bash
7npm install
8npm install stripe  # Added for payment processing

Environment Variables

bash
1STRIPE_SECRET_KEY=your_stripe_key  # Required for payments

### Setup Instructions

```bash
# You modify docker-compose.yml

# I update README:
## Development Setup

```bash
# 1. Clone repository
git clone [url]

# 2. Install dependencies
npm install

# 3. Start services (UPDATED)
docker-compose up -d  # Now includes Redis cache

# 4. Run migrations
npm run migrate

## Detection Logic

### Change Analysis

I detect these changes automatically:
- **package.json** → Update dependencies section
- **New routes** → Update API documentation
- **.env.example** → Update environment variables
- **docker-compose.yml** → Update setup instructions
- **New features** → Update features list

### Section Mapping

```yaml
Code Change → README Section:
  - New API endpoint → Usage / API Reference
  - New dependency → Installation
  - New env var → Configuration
  - New feature → Features list
  - Architecture change → Architecture section

Intelligent Updates

Keep Structure

I maintain your README structure:

• Preserve emoji style
• Keep formatting consistent
• Maintain tone and voice
• Respect existing organization

Add Missing Sections

markdown
1# Suggested additions:
2
3## Prerequisites
4- Node.js 18+
5- Docker (for development)
6- PostgreSQL 14+
7
8## Environment Variables
9```bash
10DATABASE_URL=postgresql://localhost/mydb
11API_KEY=your_api_key

Testing

bash
1npm test

### Update Examples

```markdown
# Before:
```javascript
const result = api.getUsers();

After (API changed):

javascript
1const result = await api.getUsers({ page: 1, limit: 10 });

## Version Compatibility

I track version-specific documentation:

```markdown
## Requirements

- Node.js 18+ (updated from 16+)
- TypeScript 5.0+ (new requirement)
- React 18+ (unchanged)

Changelog Integration

I can sync with CHANGELOG.md:

markdown
1## Recent Changes
2
3See [CHANGELOG.md](CHANGELOG.md) for detailed version history.
4
5### Latest (v2.1.0)
6- ✨ Added user authentication
7- 🔧 Fixed memory leak in data processing
8- 📝 Updated API documentation

Screenshot Management

markdown
1# I suggest when UI changes:
2## Screenshots
3
4![Dashboard](screenshots/dashboard.png)
5*Updated: 2025-10-24 - New authentication panel*
6
7![User Profile](screenshots/profile.png)
8*New feature - user profile management*

Relationship with @docs-writer

Me (Skill): Keep README current with code changes @docs-writer (Sub-Agent): Comprehensive documentation strategy

Workflow

1. I detect changes
2. I suggest README updates
3. For full docs → Invoke @docs-writer sub-agent
4. Sub-agent creates complete documentation

Sandboxing Compatibility

Works without sandboxing: ✅ Yes Works with sandboxing: ✅ Yes

• Filesystem: Writes to README.md
• Network: None required
• Configuration: None required

Best Practices

1. Keep it current - Update README with every feature
2. Be specific - Include version numbers, prerequisites
3. Add examples - Show actual usage, not just API
4. Include troubleshooting - Common issues and solutions
5. Badge status - Keep build/coverage badges current

README Templates

Basic Structure

markdown
1# Project Name
2
3Brief description
4
5## Features
6- Feature 1
7- Feature 2
8
9## Installation
10```bash
11npm install

Usage

javascript
1// Example

Configuration

Environment variables needed

Contributing

How to contribute

License

MIT

### Comprehensive Structure

```markdown
# Project Name
> Tagline

[Badges]

## Table of Contents
- Features
- Installation
- Usage
- API Reference
- Configuration
- Development
- Testing
- Deployment
- Contributing
- License

[Sections with detailed content]

Integration

With /docs-gen Command

bash
1/docs-gen --format markdown
2
3# Generates:
4# 1. README.md (via me)
5# 2. Full documentation site (via @docs-writer)
6# 3. API reference (via api-documenter)

With CI/CD

yaml
1# .github/workflows/docs.yml
2- name: Update README
3  run: |
4    # Skill suggests updates based on changes
5    # Review and commit

Customization

Add company-specific README standards:

bash
1cp -r ~/.claude/skills/documentation/readme-updater \
2      ~/.claude/skills/documentation/company-readme-updater
3
4# Edit to add:
5# - Company README template
6# - Required sections
7# - Badge standards

Related Tools

• api-documenter skill: API documentation
• @docs-writer sub-agent: Comprehensive docs
• git-commit-helper skill: Commit messages for updates
• /docs-gen command: Full documentation generation