About readme-updates
A writing skill for maintaining root and package README files, with structure templates, update checks, and commands for validating links and Markdown. It is intended for maintainers keeping project documentation accurate and complete.
Key features
- 01Show a root README structure example
- 02Provide a package README template
- 03List common badges and environment variable sections
- 04Include an update checklist
- 05Describe link and Markdown validation
Use cases
- 01Write a README for a new package
- 02Update feature or technology stack documentation
- 03Check setup steps and code examples
- 04Validate Markdown and links
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ motormetrics/ motormetrics --skill readme-updatesAfter installing, type/readme-updatesin Claude Code to confirm it loaded.
Details
From the project READMEREADME Updates Skill
Root README Structure
# SG Cars Trends
[](LICENSE)
[](https://github.com/sgcarstrends/sgcarstrends/actions)
> Platform for accessing Singapore vehicle registration and COE bidding data
## Features
- 📊 **Comprehensive Data**: Car registration and COE bidding data
- 🔄 **Real-time Updates**: Automated daily updates from LTA DataMall
- 📝 **AI-Generated Blog**: Automated insights using Google Gemini
## Quick Start
\`\`\`bash
git clone https://github.com/sgcarstrends/sgcarstrends.git
cd sgcarstrends
pnpm install
cp .env.example .env
pnpm db:migrate
pnpm dev
\`\`\`
## Tech Stack
- **Frontend**: Next.js 16, HeroUI v3 (+ HeroUI Pro), Tailwind CSS v4
- **Backend**: Drizzle ORM, PostgreSQL, Upstash Redis
- **Infrastructure**: Vercel
- **AI**: Google Gemini, Vercel AI SDK
## Project Structure
\`\`\`
sgcarstrends/
├── apps/
│ ├── api/ # Hono API
│ └── web/ # Next.js web app
├── packages/
│ ├── database/ # Drizzle schemas
│ ├── ui/ # UI components
│ └── utils/ # Shared utilities
\`\`\`
## Development
\`\`\`bash
pnpm dev # Start all servers
pnpm test # Run tests
pnpm build # Build for production
\`\`\`
## License
MIT
Package README Template
# @sgcarstrends/[package-name]
> Brief description
## Installation
\`\`\`bash
pnpm add @sgcarstrends/[package-name]
\`\`\`
## Usage
\`\`\`typescript
import { functionName } from "@sgcarstrends/[package-name]";
const result = functionName();
\`\`\`
## API
### `functionName(param: string): ReturnType`
Description.
**Parameters:** `param` (string) - Description
**Returns:** `ReturnType` - Description
## Development
\`\`\`bash
pnpm test
pnpm build
\`\`\`
## License
MIT
Common Badges
[](LICENSE)
[](actions)
[](npm)
[](typescript)
Environment Variables Section
## Environment Variables
Create `.env` from `.env.example`:
\`\`\`env
DATABASE_URL=postgresql://user:pass@localhost:5432/db
UPSTASH_REDIS_REST_URL=https://your-redis.upstash.io
UPSTASH_REDIS_REST_TOKEN=your-token
\`\`\`
Update Checklist
- Features list current when new features added
- Tech stack updated when dependencies change
- Setup instructions accurate when process changes
- Examples working and up-to-date
- Links not broken
Validate README
# Check for broken links
pnpm dlx markdown-link-check README.md
# Lint markdown
pnpm dlx markdownlint README.md
Best Practices
- Clear Description: Concise project description at top
- Quick Start: Immediate value with copy-paste setup
- Working Examples: Test all code examples
- Keep Updated: Update when features change
- Check Links: Regularly verify links work
References
- Shields.io: https://shields.io (badges)
- markdownlint: https://github.com/DavidAnson/markdownlint
Comments
Markdown supported