make-release-readme

Automate release-ready README creation with embedded Playwright screenshots.

2|1|Updated Sep 28, 2023
One-click install
npx skills add https://github.com/vmasrani/dotfiles --skill make-release-readme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-release-readme
Source: https://github.com/vmasrani/dotfiles/tree/main/maintained_global_claude/skills/make-release-readme
Command: npx skills add https://github.com/vmasrani/dotfiles --skill make-release-readme

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pillow, typer, loguru, and includes scripts (resource) components.

What problem does it solve?

Creating consistent, polished README documentation with visuals is time-consuming and error-prone; this skill automates it, producing a release-ready document with embedded screenshots.

Core Features & Use Cases

  • Automated feature inventory: reads the codebase to identify app features and generate a feature list for the README.
  • Screenshot campaign orchestration: uses Playwright to take screenshots across desktop/tablet/mobile viewports for key routes/pages.
  • Markdown generation: compiles a structured README including installation, usage, tech stack, and project details, ready for publishing.

Quick Start

Run the tool from your project root to generate a release-ready README.md with embedded screenshots.

Frequently Asked Questions about make-release-readme

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

FAQPage Schema
How do I automate README generation with Playwright screenshots for a web app?

Automate README generation by running a script that scans your codebase to inventory features, orchestrates a Playwright screenshot campaign across desktop, tablet, and mobile viewports, and compiles a structured markdown document with installation and usage details.

What is the best way to create a release-ready README with embedded screenshots?

The best way to create a release-ready README is to automate the process using a tool that reads your project features, captures embedded screenshots across multiple viewports, and compiles the text and images into a publishable markdown file.

How does automated feature inventory work for markdown documentation?

Automated feature inventory works by scanning the codebase to identify app features, then passing that extracted list into the markdown generation process to populate the structured README with accurate project details and usage information.

Does the screenshot campaign support mobile and tablet viewports?

Yes, the screenshot campaign supports mobile and tablet viewports by using Playwright to capture responsive screenshots of key routes, ensuring the generated README includes visuals for desktop, tablet, and mobile layouts.

Do I need a specific project layout to generate a README with screenshots?

Yes, you need a predictable project layout so the script can scan the codebase and identify key routes to screenshot, ensuring the Playwright campaign and markdown compilation produce a structured, release-ready document.

What limitations exist when automating markdown documentation with Playwright?

Limitations include relying on a predictable project layout to inventory features accurately, requiring Playwright to access web app routes, and depending on Python dependencies like pillow, typer, and loguru to compile the structured markdown file.