write-doc-markdown

Draft WordPress-style Markdown posts from the current repository state.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/tubtrb/autoreport --skill write-doc-markdown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-doc-markdown
Source: https://github.com/tubtrb/autoreport/tree/main/codex/skills/write-doc-markdown
Command: npx skills add https://github.com/tubtrb/autoreport --skill write-doc-markdown

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Codex often needs to draft public-facing Markdown posts that accurately reflect the current state of the autoreport repository. This skill provides a reliable workflow to generate WordPress-style posts that align with existing writing patterns and documentation.

Core Features & Use Cases

  • Supports three modes: 개발 일지, 릴리즈 노트, and 사용 가이드.
  • Grounds posts in repo truth by referencing the version in pyproject.toml, local date, tests, README, and package metadata, ensuring factual accuracy.
  • Produces publish-ready Markdown with a consistent voice and structure, ready for publishing or handoff to autorelease.

Quick Start

Choose a mode (개발 일지, 릴리즈 노트, or 사용 가이드) and draft a publish-ready Markdown post grounded in the current repository state.

Frequently Asked Questions about write-doc-markdown

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

FAQPage Schema
How do I draft WordPress Markdown posts from my repository state?

You can draft WordPress Markdown posts by reading repository truth like pyproject.toml versions, local dates, tests, and README metadata. The skill grounds content in these sources to produce publish-ready Markdown documents with consistent structure.

What is the best way to generate a development log from repo metadata?

Generating a development log from repo metadata involves referencing pyproject.toml versioning, package metadata, and tests. The skill applies these repository truths to a fixed mode, ensuring factual accuracy and style-reference compliance for public-facing posts.

Can I write release notes and user guides grounded in repository truth?

Yes, you can write release notes and user guides grounded in repository truth. The skill supports three fixed modes—development log, release notes, and user guide—each ensuring version, date, and metadata grounding for accurate documentation.

Does this documentation approach ensure compliance with existing style guides?

Documentation generated through this approach ensures style-reference compliance by aligning with existing writing patterns. It grounds all content in repository truth, applying a consistent voice and structure to produce Markdown ready for WordPress publishing or autorelease handoff.

What are the limitations of automated Markdown documentation from repo state?

Automated Markdown documentation from repo state is limited to three fixed modes: development log, release notes, and user guide. It relies strictly on available repository metadata like pyproject.toml and README, meaning incomplete repo data will affect factual grounding.

Do I need specific dependencies to draft publish-ready Markdown from my repository?

No specific dependencies are required to draft publish-ready Markdown from your repository. The skill operates without external dependencies, directly reading repository metadata to generate WordPress-style posts grounded in current autoreport state.