dotmd-parser 0.2.0__tar.gz → 0.5.0__tar.gz

dotmd_parser-0.5.0/PKG-INFO

@@ -0,0 +1,318 @@
+Metadata-Version: 2.4
+Name: dotmd-parser
+Version: 0.5.0
+Summary: Dependency graph parser and AI analyzer for .md skill files — parse @include/@delegate/@ref directives, build graphs, resolve templates, and detect implicit dependencies via Claude for AI agent prompt engineering
+Author: dotmd-projects
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/dotmd-projects/dotmd-parser
+Project-URL: Repository, https://github.com/dotmd-projects/dotmd-parser
+Project-URL: Issues, https://github.com/dotmd-projects/dotmd-parser/issues
+Keywords: claude-code,ai-agent,skill-management,prompt-engineering,dependency-graph,SKILL.md,markdown,parser,dotmd,llm
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Software Development :: Code Generators
+Classifier: Topic :: Text Processing :: Markup :: Markdown
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# dotmd-parser
+
+[![PyPI version](https://img.shields.io/pypi/v/dotmd-parser)](https://pypi.org/project/dotmd-parser/)
+[![Python](https://img.shields.io/pypi/pyversions/dotmd-parser)](https://pypi.org/project/dotmd-parser/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
+
+![dotmd-parser demo](assets/demo.gif)
+
+> [日本語版 README はこちら](README.ja.md)
+
+Dependency graph parser for `.md` skill files — built for AI agent prompt engineering with [Claude Code](https://docs.anthropic.com/en/docs/claude-code) and similar tools.
+
+## Why dotmd-parser?
+
+As AI agent projects grow, `.md` files start referencing each other via `@include`, `@delegate`, and `@ref` directives. Without tooling, you're left manually tracing dependencies to answer basic questions:
+
+- *"Which files break if I edit `shared/role.md`?"*
+- *"Is there a circular reference hiding in my skill tree?"*
+- *"What `{{variables}}` are still unresolved after expansion?"*
+
+**dotmd-parser** solves this by parsing your `.md` files into a dependency graph — automatically detecting directives, runtime references, and template placeholders. One function call gives you the full picture.
+
+## Comparison
+
+| Capability | Manual / grep | dotmd-parser |
+|---|---|---|
+| Find `@include` / `@delegate` / `@ref` references | `grep -r "@include"` — flat list, no context | Structured graph with node types and edge metadata |
+| Detect circular references | Hope you notice before the agent loops | Automatic detection with full cycle path in warnings |
+| Reverse dependency ("what breaks?") | Manually trace every file | `dependents_of(graph, "shared/role.md")` — one call |
+| Expand `@include` to final text | Copy-paste by hand | `resolve("SKILL.md", variables={...})` — recursive expansion |
+| Find unresolved `{{variables}}` | `grep "{{" *.md` — noisy, no dedup | Deduplicated list per node and after expansion |
+| Missing file detection | Runtime failure | Warnings at parse time with exact paths |
+| Detect **implicit** deps (no directives yet) | Read every file, draw by hand | `analyze` subcommand asks Claude, emits `@include` / `deps.yml` |
+| Feed Claude Code with compact context | Read 20 files × 5 KB each | `digest` outputs one ~2 KB summary; `.claude/dotmd-index.json` cache |
+
+## Installation
+
+```bash
+pip install dotmd-parser
+```
+
+## Quick Start
+
+```python
+from dotmd_parser import build_graph, resolve, dependents_of, summary
+```
+
+### build_graph — Build a dependency graph
+
+```python
+graph = build_graph("./my-skill/")
+# or from a specific file
+graph = build_graph("./my-skill/SKILL.md")
+```
+
+Returns:
+
+```json
+{
+  "nodes": [
+    {"id": "/abs/path/to/SKILL.md", "type": "skill", "missing": false, "placeholders": []}
+  ],
+  "edges": [
+    {"from": "...", "to": "...", "type": "include", "parallel": false}
+  ],
+  "warnings": []
+}
+```
+
+**Custom node type mapping:**
+
+By default, node types are inferred from path keywords (`agent`, `shared`, `prompt`, `reference`, `asset`, `template`). You can override this with the `type_map` parameter:
+
+```python
+graph = build_graph("./my-skill/", type_map=[
+    ("helper", "utility"),
+    ("core", "foundation"),
+])
+```
+
+**deps.yml support:**
+
+If a `deps.yml` file exists in the root directory, its dependencies are automatically merged into the graph:
+
+```yaml
+- path: agents/planner.md
+  includes:
+    - shared/role.md
+    - shared/tools.md
+```
+
+### resolve — Expand @include directives
+
+Recursively expands `@include` directives into final text. `@delegate` and `@ref` lines are left as-is.
+
+```python
+result = resolve("./prompts/main.md", variables={"name": "Alice"})
+
+print(result["content"])       # Fully expanded text
+print(result["placeholders"])  # Unresolved {{variable}} names
+print(result["warnings"])      # Circular refs, missing files, etc.
+```
+
+### dependents_of — Reverse dependency query
+
+```python
+# "If I change shared/role.md, what else breaks?"
+affected = dependents_of(graph, "/abs/path/to/shared/role.md")
+```
+
+### summary — Human-readable overview
+
+```python
+print(summary(graph))
+# Nodes: 5  (agent:1, prompt:1, shared:2, skill:1)
+# Edges: 4  (include:2, ref:1, read-ref:1)
+# Warnings: 0
+# Placeholders: name, role
+```
+
+## Supported Directives
+
+| Directive | Edge type | Expanded by `resolve()`? | Description |
+|---|---|---|---|
+| `@include path/to/file.md` | `include` | Yes | Inline expansion — file content is inserted at this position |
+| `@delegate path/to/agent.md` | `delegate` | No | Agent delegation — recorded in graph, left as-is in output |
+| `@delegate path/to/agent.md --parallel` | `delegate` | No | Parallel delegation with `--parallel` flag |
+| `@ref path/to/file.md` | `ref` | No | Runtime reference — recorded in graph, left as-is in output |
+| `` Read `path/to/file.md` `` | `read-ref` | No | Legacy runtime reference (same as `@ref`, kept for backward compatibility) |
+
+## Utility Functions
+
+Lower-level parsing functions are also exported for custom use:
+
+```python
+from dotmd_parser import parse_directives, parse_read_refs, parse_placeholders, parse_deps_yml
+```
+
+| Function | Description |
+|---|---|
+| `parse_directives(content)` | Extract `@include` / `@delegate` / `@ref` directives from text |
+| `parse_read_refs(content)` | Extract legacy `Read`/`See`/list-style `.md` references (deduplicated) |
+| `parse_placeholders(content)` | Extract `{{variable}}` placeholder names (deduplicated) |
+| `parse_deps_yml(content)` | Parse `deps.yml` text into `{path: [includes]}` dict (no PyYAML required) |
+
+## CLI
+
+`dotmd-parser` ships with sub-commands tuned for Claude Code and CI use. Running `dotmd-parser <path>` with no sub-command still works and falls through to `show` for backward compatibility.
+
+| Command | Purpose |
+|---|---|
+| `dotmd-parser inventory <path>` | **API-free**: extension counts, markdown/binary ratio, largest files |
+| `dotmd-parser index <path>` | Build and save `.claude/dotmd-index.json` |
+| `dotmd-parser index <path> --scope <subdir>` | Incrementally re-index one subfolder, merge into the existing index |
+| `dotmd-parser check <path>` | Exit non-zero on cycles / missing refs (CI-friendly) |
+| `dotmd-parser affects <path> <file>` | Reverse dependencies of `<file>` |
+| `dotmd-parser deps <path> <file>` | Direct dependencies of `<file>` |
+| `dotmd-parser digest <path>` | Token-efficient text summary for LLM context |
+| `dotmd-parser tree <path>` | ASCII dependency tree |
+| `dotmd-parser resolve <file> [--var k=v]` | Recursively expand `@include` |
+| `dotmd-parser analyze <path>` | AI dependency detection (requires `ANTHROPIC_API_KEY`) |
+| `dotmd-parser analyze <path> --dry-run` | **API-free**: estimate tokens and USD cost |
+| `dotmd-parser analyze <path> --plan` | **API-free**: emit a host-agent prompt pack for Claude Code to execute |
+| `dotmd-parser analyze <path> --apply-from <json>` | Apply a pre-computed analysis JSON |
+| `dotmd-parser show <path>` | Summary + full JSON graph (legacy default) |
+
+```bash
+# Typical Claude Code workflow
+dotmd-parser inventory ./my-skill/       # start here if you've never seen the folder
+dotmd-parser index ./my-skill/           # one-off; cached until files change
+dotmd-parser digest ./my-skill/          # compact summary for the LLM
+dotmd-parser affects ./my-skill/ shared/role.md
+```
+
+## `analyze` — AI-assisted dependency detection
+
+Use when a folder of markdown has **no explicit directives yet**. `analyze`
+asks Claude to infer dependencies and can apply the result in one step:
+
+```bash
+export ANTHROPIC_API_KEY=...   # or put it in ./.env
+
+dotmd-parser analyze ./docs/              # runs the proposal (uses API)
+dotmd-parser analyze ./docs/ --apply      # inject @include, write deps.yml
+dotmd-parser analyze ./docs/ --json       # machine-readable
+dotmd-parser analyze ./docs/ --ext md --ext pdf --ext docx
+```
+
+### No-API-key workflows
+
+```bash
+# Estimate cost before spending any API credit
+dotmd-parser analyze ./docs/ --dry-run
+
+# Delegate the analysis to Claude Code itself — no API key needed
+dotmd-parser analyze ./docs/ --plan > plan.md
+#   1. Claude Code reads plan.md and executes the task locally
+#   2. It writes the result to analysis.json
+#   3. Apply it:
+dotmd-parser analyze ./docs/ --apply-from analysis.json
+```
+
+- Text files (`.md`, `.txt`, etc.) get `@include` lines prepended.
+- Binary sources (`.pdf`, `.docx`) are recorded in `deps.yml` — they can't
+  be edited in-place, so the parser reads them from there.
+- PDF / DOCX support is optional: `pip install pdfplumber python-docx`.
+- Re-run with `--apply` over time as the repo grows — existing directives
+  are preserved.
+
+The bundled prompt lives at
+`src/dotmd_parser/templates/prompts/analyze-dependencies.md` and is shipped
+inside the wheel; no network access is needed except for the Claude API
+call itself.
+
+### Programmatic use
+
+```python
+from dotmd_parser import analyze_dependencies, apply_analysis
+
+proposal = analyze_dependencies("./docs/")
+print(proposal["edges"])
+apply_analysis("./docs/", proposal)
+```
+
+For offline tests, pass a `caller=...` kwarg that returns a stub JSON string.
+
+## Claude Code Skill integration
+
+A ready-to-use Claude Code Skill is bundled with the package at
+`src/dotmd_parser/templates/SKILL.md`. Three install paths:
+
+```bash
+# via pip — installs the CLI and drops SKILL.md into the current project
+pip install dotmd-parser
+dotmd-parser init .
+
+# via Release archive — no pip required
+mkdir -p .claude/skills
+curl -L https://github.com/dotmd-projects/dotmd-parser/releases/latest/download/skill.tar.gz \
+  | tar -xz -C .claude/skills/
+
+# manual
+cp src/dotmd_parser/templates/SKILL.md \
+   /path/to/project/.claude/skills/dotmd-parser/
+```
+
+Once installed, Claude will consult the skill whenever it encounters
+`SKILL.md`, `deps.yml`, a `.claude/skills/` tree, or is asked about
+dependencies of a markdown file.
+
+**Why this saves tokens.** Without the skill, Claude typically `grep -r`s
+for `@include`/`@ref` and `cat`s every referenced file to trace a graph.
+With the skill it reads `.claude/dotmd-index.json` (compact, relative paths,
+first-paragraph descriptions) or the `digest` output once, then queries
+`affects` / `deps` by name — never touching the raw markdown until an edit
+is actually needed.
+
+### Auto-refresh via Hook (optional)
+
+Add to `~/.claude/settings.json` to keep `.claude/dotmd-index.json` fresh
+after every markdown edit:
+
+```json
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write",
+        "command": "dotmd-parser index \"$CLAUDE_PROJECT_DIR\" >/dev/null 2>&1 || true"
+      }
+    ]
+  }
+}
+```
+
+The command is idempotent (SHA-256 cache) and exits fast when nothing
+changed.
+
+## Development
+
+```bash
+git clone https://github.com/dotmd-projects/dotmd-parser.git
+cd dotmd-parser
+pip install -e .
+pip install pytest
+pytest tests/ -v
+```
+
+## License
+
+MIT

dotmd_parser-0.5.0/README.md

@@ -0,0 +1,291 @@
+# dotmd-parser
+
+[![PyPI version](https://img.shields.io/pypi/v/dotmd-parser)](https://pypi.org/project/dotmd-parser/)
+[![Python](https://img.shields.io/pypi/pyversions/dotmd-parser)](https://pypi.org/project/dotmd-parser/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
+
+![dotmd-parser demo](assets/demo.gif)
+
+> [日本語版 README はこちら](README.ja.md)
+
+Dependency graph parser for `.md` skill files — built for AI agent prompt engineering with [Claude Code](https://docs.anthropic.com/en/docs/claude-code) and similar tools.
+
+## Why dotmd-parser?
+
+As AI agent projects grow, `.md` files start referencing each other via `@include`, `@delegate`, and `@ref` directives. Without tooling, you're left manually tracing dependencies to answer basic questions:
+
+- *"Which files break if I edit `shared/role.md`?"*
+- *"Is there a circular reference hiding in my skill tree?"*
+- *"What `{{variables}}` are still unresolved after expansion?"*
+
+**dotmd-parser** solves this by parsing your `.md` files into a dependency graph — automatically detecting directives, runtime references, and template placeholders. One function call gives you the full picture.
+
+## Comparison
+
+| Capability | Manual / grep | dotmd-parser |
+|---|---|---|
+| Find `@include` / `@delegate` / `@ref` references | `grep -r "@include"` — flat list, no context | Structured graph with node types and edge metadata |
+| Detect circular references | Hope you notice before the agent loops | Automatic detection with full cycle path in warnings |
+| Reverse dependency ("what breaks?") | Manually trace every file | `dependents_of(graph, "shared/role.md")` — one call |
+| Expand `@include` to final text | Copy-paste by hand | `resolve("SKILL.md", variables={...})` — recursive expansion |
+| Find unresolved `{{variables}}` | `grep "{{" *.md` — noisy, no dedup | Deduplicated list per node and after expansion |
+| Missing file detection | Runtime failure | Warnings at parse time with exact paths |
+| Detect **implicit** deps (no directives yet) | Read every file, draw by hand | `analyze` subcommand asks Claude, emits `@include` / `deps.yml` |
+| Feed Claude Code with compact context | Read 20 files × 5 KB each | `digest` outputs one ~2 KB summary; `.claude/dotmd-index.json` cache |
+
+## Installation
+
+```bash
+pip install dotmd-parser
+```
+
+## Quick Start
+
+```python
+from dotmd_parser import build_graph, resolve, dependents_of, summary
+```
+
+### build_graph — Build a dependency graph
+
+```python
+graph = build_graph("./my-skill/")
+# or from a specific file
+graph = build_graph("./my-skill/SKILL.md")
+```
+
+Returns:
+
+```json
+{
+  "nodes": [
+    {"id": "/abs/path/to/SKILL.md", "type": "skill", "missing": false, "placeholders": []}
+  ],
+  "edges": [
+    {"from": "...", "to": "...", "type": "include", "parallel": false}
+  ],
+  "warnings": []
+}
+```
+
+**Custom node type mapping:**
+
+By default, node types are inferred from path keywords (`agent`, `shared`, `prompt`, `reference`, `asset`, `template`). You can override this with the `type_map` parameter:
+
+```python
+graph = build_graph("./my-skill/", type_map=[
+    ("helper", "utility"),
+    ("core", "foundation"),
+])
+```
+
+**deps.yml support:**
+
+If a `deps.yml` file exists in the root directory, its dependencies are automatically merged into the graph:
+
+```yaml
+- path: agents/planner.md
+  includes:
+    - shared/role.md
+    - shared/tools.md
+```
+
+### resolve — Expand @include directives
+
+Recursively expands `@include` directives into final text. `@delegate` and `@ref` lines are left as-is.
+
+```python
+result = resolve("./prompts/main.md", variables={"name": "Alice"})
+
+print(result["content"])       # Fully expanded text
+print(result["placeholders"])  # Unresolved {{variable}} names
+print(result["warnings"])      # Circular refs, missing files, etc.
+```
+
+### dependents_of — Reverse dependency query
+
+```python
+# "If I change shared/role.md, what else breaks?"
+affected = dependents_of(graph, "/abs/path/to/shared/role.md")
+```
+
+### summary — Human-readable overview
+
+```python
+print(summary(graph))
+# Nodes: 5  (agent:1, prompt:1, shared:2, skill:1)
+# Edges: 4  (include:2, ref:1, read-ref:1)
+# Warnings: 0
+# Placeholders: name, role
+```
+
+## Supported Directives
+
+| Directive | Edge type | Expanded by `resolve()`? | Description |
+|---|---|---|---|
+| `@include path/to/file.md` | `include` | Yes | Inline expansion — file content is inserted at this position |
+| `@delegate path/to/agent.md` | `delegate` | No | Agent delegation — recorded in graph, left as-is in output |
+| `@delegate path/to/agent.md --parallel` | `delegate` | No | Parallel delegation with `--parallel` flag |
+| `@ref path/to/file.md` | `ref` | No | Runtime reference — recorded in graph, left as-is in output |
+| `` Read `path/to/file.md` `` | `read-ref` | No | Legacy runtime reference (same as `@ref`, kept for backward compatibility) |
+
+## Utility Functions
+
+Lower-level parsing functions are also exported for custom use:
+
+```python
+from dotmd_parser import parse_directives, parse_read_refs, parse_placeholders, parse_deps_yml
+```
+
+| Function | Description |
+|---|---|
+| `parse_directives(content)` | Extract `@include` / `@delegate` / `@ref` directives from text |
+| `parse_read_refs(content)` | Extract legacy `Read`/`See`/list-style `.md` references (deduplicated) |
+| `parse_placeholders(content)` | Extract `{{variable}}` placeholder names (deduplicated) |
+| `parse_deps_yml(content)` | Parse `deps.yml` text into `{path: [includes]}` dict (no PyYAML required) |
+
+## CLI
+
+`dotmd-parser` ships with sub-commands tuned for Claude Code and CI use. Running `dotmd-parser <path>` with no sub-command still works and falls through to `show` for backward compatibility.
+
+| Command | Purpose |
+|---|---|
+| `dotmd-parser inventory <path>` | **API-free**: extension counts, markdown/binary ratio, largest files |
+| `dotmd-parser index <path>` | Build and save `.claude/dotmd-index.json` |
+| `dotmd-parser index <path> --scope <subdir>` | Incrementally re-index one subfolder, merge into the existing index |
+| `dotmd-parser check <path>` | Exit non-zero on cycles / missing refs (CI-friendly) |
+| `dotmd-parser affects <path> <file>` | Reverse dependencies of `<file>` |
+| `dotmd-parser deps <path> <file>` | Direct dependencies of `<file>` |
+| `dotmd-parser digest <path>` | Token-efficient text summary for LLM context |
+| `dotmd-parser tree <path>` | ASCII dependency tree |
+| `dotmd-parser resolve <file> [--var k=v]` | Recursively expand `@include` |
+| `dotmd-parser analyze <path>` | AI dependency detection (requires `ANTHROPIC_API_KEY`) |
+| `dotmd-parser analyze <path> --dry-run` | **API-free**: estimate tokens and USD cost |
+| `dotmd-parser analyze <path> --plan` | **API-free**: emit a host-agent prompt pack for Claude Code to execute |
+| `dotmd-parser analyze <path> --apply-from <json>` | Apply a pre-computed analysis JSON |
+| `dotmd-parser show <path>` | Summary + full JSON graph (legacy default) |
+
+```bash
+# Typical Claude Code workflow
+dotmd-parser inventory ./my-skill/       # start here if you've never seen the folder
+dotmd-parser index ./my-skill/           # one-off; cached until files change
+dotmd-parser digest ./my-skill/          # compact summary for the LLM
+dotmd-parser affects ./my-skill/ shared/role.md
+```
+
+## `analyze` — AI-assisted dependency detection
+
+Use when a folder of markdown has **no explicit directives yet**. `analyze`
+asks Claude to infer dependencies and can apply the result in one step:
+
+```bash
+export ANTHROPIC_API_KEY=...   # or put it in ./.env
+
+dotmd-parser analyze ./docs/              # runs the proposal (uses API)
+dotmd-parser analyze ./docs/ --apply      # inject @include, write deps.yml
+dotmd-parser analyze ./docs/ --json       # machine-readable
+dotmd-parser analyze ./docs/ --ext md --ext pdf --ext docx
+```
+
+### No-API-key workflows
+
+```bash
+# Estimate cost before spending any API credit
+dotmd-parser analyze ./docs/ --dry-run
+
+# Delegate the analysis to Claude Code itself — no API key needed
+dotmd-parser analyze ./docs/ --plan > plan.md
+#   1. Claude Code reads plan.md and executes the task locally
+#   2. It writes the result to analysis.json
+#   3. Apply it:
+dotmd-parser analyze ./docs/ --apply-from analysis.json
+```
+
+- Text files (`.md`, `.txt`, etc.) get `@include` lines prepended.
+- Binary sources (`.pdf`, `.docx`) are recorded in `deps.yml` — they can't
+  be edited in-place, so the parser reads them from there.
+- PDF / DOCX support is optional: `pip install pdfplumber python-docx`.
+- Re-run with `--apply` over time as the repo grows — existing directives
+  are preserved.
+
+The bundled prompt lives at
+`src/dotmd_parser/templates/prompts/analyze-dependencies.md` and is shipped
+inside the wheel; no network access is needed except for the Claude API
+call itself.
+
+### Programmatic use
+
+```python
+from dotmd_parser import analyze_dependencies, apply_analysis
+
+proposal = analyze_dependencies("./docs/")
+print(proposal["edges"])
+apply_analysis("./docs/", proposal)
+```
+
+For offline tests, pass a `caller=...` kwarg that returns a stub JSON string.
+
+## Claude Code Skill integration
+
+A ready-to-use Claude Code Skill is bundled with the package at
+`src/dotmd_parser/templates/SKILL.md`. Three install paths:
+
+```bash
+# via pip — installs the CLI and drops SKILL.md into the current project
+pip install dotmd-parser
+dotmd-parser init .
+
+# via Release archive — no pip required
+mkdir -p .claude/skills
+curl -L https://github.com/dotmd-projects/dotmd-parser/releases/latest/download/skill.tar.gz \
+  | tar -xz -C .claude/skills/
+
+# manual
+cp src/dotmd_parser/templates/SKILL.md \
+   /path/to/project/.claude/skills/dotmd-parser/
+```
+
+Once installed, Claude will consult the skill whenever it encounters
+`SKILL.md`, `deps.yml`, a `.claude/skills/` tree, or is asked about
+dependencies of a markdown file.
+
+**Why this saves tokens.** Without the skill, Claude typically `grep -r`s
+for `@include`/`@ref` and `cat`s every referenced file to trace a graph.
+With the skill it reads `.claude/dotmd-index.json` (compact, relative paths,
+first-paragraph descriptions) or the `digest` output once, then queries
+`affects` / `deps` by name — never touching the raw markdown until an edit
+is actually needed.
+
+### Auto-refresh via Hook (optional)
+
+Add to `~/.claude/settings.json` to keep `.claude/dotmd-index.json` fresh
+after every markdown edit:
+
+```json
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write",
+        "command": "dotmd-parser index \"$CLAUDE_PROJECT_DIR\" >/dev/null 2>&1 || true"
+      }
+    ]
+  }
+}
+```
+
+The command is idempotent (SHA-256 cache) and exits fast when nothing
+changed.
+
+## Development
+
+```bash
+git clone https://github.com/dotmd-projects/dotmd-parser.git
+cd dotmd-parser
+pip install -e .
+pip install pytest
+pytest tests/ -v
+```
+
+## License
+
+MIT

{dotmd_parser-0.2.0 → dotmd_parser-0.5.0}/pyproject.toml

@@ -1,7 +1,7 @@
 [project]
 name = "dotmd-parser"
-version = "0.2.0"
-description = "Dependency graph parser for .md skill files — parse @include/@delegate/@ref directives, build graphs, and resolve templates for AI agent prompt engineering"
+version = "0.5.0"
+description = "Dependency graph parser and AI analyzer for .md skill files — parse @include/@delegate/@ref directives, build graphs, resolve templates, and detect implicit dependencies via Claude for AI agent prompt engineering"
 requires-python = ">=3.10"
 license = "MIT"
 readme = "README.md"
@@ -50,5 +50,9 @@ build-backend = "setuptools.build_meta"
 [tool.setuptools.packages.find]
 where = ["src"]
 
+[tool.setuptools.package-data]
+"dotmd_parser.templates" = ["*.md"]
+"dotmd_parser.templates.prompts" = ["*.md"]
+
 [tool.pytest.ini_options]
 testpaths = ["tests"]