How do I install the Jo Minjun Petrify Align Readme skill?

Run npx skillmds@latest add tomevault-io/jo-minjun-petrify-align-readme in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Jo Minjun Petrify Align Readme skill do?

Align README It is listed under Coding & Dev Tools on SkillMD.

Is Jo Minjun Petrify Align Readme safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jo Minjun Petrify Align Readme?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jo Minjun Petrify Align Readme free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Jo Minjun Petrify Align Readme?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jo Minjun Petrify Align Readme by tomevault-io

Name: Jo Minjun Petrify Align Readme
Author: tomevault-io

File contents

Align README

Scan the codebase and interactively synchronize README.md and CONTRIBUTING.md with code reality.

Code is the source of truth. AGENTS.md is read-only reference (use align-architecture to audit code against AGENTS.md — this skill does the reverse).

Process

1. Scan Codebase

Collect current state from code:

Packages — Read pnpm-workspace.yaml to get package globs, then find all matching package.json files. Extract each name field. Build the directory tree.

Ports & Adapters — Read packages/core/src/ports/*.ts for port interface names. Search adapter src/ dirs for implements <PortName> to build the mapping. Note supported file extensions per adapter.

Plugin Settings — Read packages/obsidian-plugin/src/settings-tab.ts. Extract setting names and descriptions from the UI registration code.

Plugin Features — Read packages/obsidian-plugin/src/main.ts and related files. Identify registered commands, event handlers, and capabilities.

2. Parse Documents

Read README.md and CONTRIBUTING.md. Split into auditable sections:

README.md:

Supported list (Parser, OCR, Output, Watcher)
Planned items
Features list
Settings table
Requirements

CONTRIBUTING.md:

Package structure tree
Port-Adapter mapping table
Data flow diagram
New adapter checklist

3. Compare & Update (Section by Section)

Process each section in order (README first, then CONTRIBUTING):

Compare code-collected data against document content
If matching → report PASS, move on
If discrepancy found:
- Show what the document says vs what the code shows
- Propose specific edits
- Ask user: approve / modify / skip
- Apply on approval

Preserve existing document formatting and style. Change only what is necessary.

4. Report

After all sections are processed, print a summary:

## align-readme Results

| Document | Section | Status |
|----------|---------|--------|
| README.md | Supported list | PASS / UPDATED / SKIPPED |
| ... | ... | ... |

Checked: N sections | Passed: N | Updated: N | Skipped: N

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: jo-minjun-petrify-align-readmedescription: Align README---# Align READMEScan the codebase and interactively synchronize README.md and CONTRIBUTING.md with code reality.**Code is the source of truth.** AGENTS.md is read-only reference (use `align-architecture` to audit code against AGENTS.md — this skill does the reverse).## Process### 1. Scan CodebaseCollect current state from code:**Packages** — Read `pnpm-workspace.yaml` to get package globs, then find all matching `package.json` files. Extract each `name` field. Build the directory tree.**Ports & Adapters** — Read `packages/core/src/ports/*.ts` for port interface names. Search adapter `src/` dirs for `implements <PortName>` to build the mapping. Note supported file extensions per adapter.**Plugin Settings** — Read `packages/obsidian-plugin/src/settings-tab.ts`. Extract setting names and descriptions from the UI registration code.**Plugin Features** — Read `packages/obsidian-plugin/src/main.ts` and related files. Identify registered commands, event handlers, and capabilities.### 2. Parse DocumentsRead README.md and CONTRIBUTING.md. Split into auditable sections:**README.md:**- Supported list (Parser, OCR, Output, Watcher)- Planned items- Features list- Settings table- Requirements**CONTRIBUTING.md:**- Package structure tree- Port-Adapter mapping table- Data flow diagram- New adapter checklist### 3. Compare & Update (Section by Section)Process each section in order (README first, then CONTRIBUTING):1. Compare code-collected data against document content2. If **matching** → report `PASS`, move on3. If **discrepancy found**: - Show what the document says vs what the code shows - Propose specific edits - Ask user: approve / modify / skip - Apply on approvalPreserve existing document formatting and style. Change only what is necessary.### 4. ReportAfter all sections are processed, print a summary:```## align-readme Results| Document | Section | Status ||----------|---------|--------|| README.md | Supported list | PASS / UPDATED / SKIPPED || ... | ... | ... |Checked: N sections | Passed: N | Updated: N | Skipped: N```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/jo-minjun) — claim your Tome and manage your conversions.

Frequently asked questions

Jo Minjun Petrify Align Readme