skills.rest
adhi-jp
adhi-jpCOMMUNITY
Explore all skills by this author →
GitHub

vibe-writing

Draft and polish development text with contract-like clarity and evidence.

Updated Mar 1, 2026
Search Tags:#documentation#writing#llm#evidence#guidelines#contract#vibe-coding
One-click install
npx skills add https://github.com/adhi-jp/agent-skills --skill vibe-writing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vibe-writing
Source: https://github.com/adhi-jp/agent-skills/tree/main/skills/vibe-writing
Command: npx skills add https://github.com/adhi-jp/agent-skills --skill vibe-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Write and polish durable development text with contract-like clarity and evidence for the next reader.

Core Features & Use Cases

  • Draft and revise README sections, changelogs, PR descriptions, and docs with precise, evidence-backed language.
  • Preserve contracts, anchors, and exact terminology such as file paths, identifiers, API names, and error messages.
  • Use-case example: Imagine updating a project README with a changelog entry that precisely states the behavior change and verification status.

Quick Start

Provide a draft or revision of a development text artifact (README, changelog, or PR description) that preserves contracts, anchors, and exact terminology.

Frequently Asked Questions about vibe-writing

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

FAQPage Schema
How do I write a changelog entry that preserves exact file paths and error messages?▼

Draft development text like changelogs using evidence-backed language that preserves contracts, anchors, file paths, identifiers, and exact error messages to ensure precision for the next reader.

What is evidence-backed writing for development documentation?▼

Evidence-backed documentation drafting is the process of writing README sections and PR descriptions with contract-like clarity, preserving exact terminology and avoiding injected context or unauthorized commits.

Can I use this to revise a PR description without losing API names and identifiers?▼

Yes, you can revise PR descriptions while preserving contracts, anchors, API names, and exact terminology, ensuring the text maintains contract-like clarity without altering the original technical evidence.

How do I polish README sections for vibe-coding workflows?▼

Polish README sections by providing an existing draft to refine, applying contract-like clarity and evidence-backed language to ensure durable development text across vibe-coding workflows.

What are the limitations of automated documentation drafting?▼

Automated documentation drafting avoids injecting new context and will not perform commits unless explicitly instructed, limiting its scope to polishing existing text rather than generating new architectural decisions.

What's the best way to document behavior changes in a project README?▼

Document behavior changes by drafting changelog entries with precise, evidence-backed language that states the exact modification and verification status while preserving file paths and identifiers.

Related Skills

Explore More Content & Communication Skills→
Light0305Light0305
514

light-paper-polishing

Polish academic manuscripts across language, structure, and argumentation.

Community
Advanced
hpsgdhpsgd

style-guide

Rewrite technical docs, commit messages, and PR descriptions for consistent tone.

Official
Advanced
spences10spences10
59

blog-post-creator

Generate blog post drafts with frontmatter and a four-section structure.

Community
Basic
criccominicriccomini
42

write-like-paul-graham

Draft and revise essays with thesis-first structure and plain diction.

Community
Intermediate