prompt_manager 1.0.1 → 1.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8f6339dd195179a1d9d9f996d1dfc4d0c689a3ed4bb9415fe2d5d68eaaa761ba
-  data.tar.gz: 2b443af6d4ea259fd124c6ff9d225129d0e233fbffc0d9e86a42ce2189595f29
+  metadata.gz: f2de9f9b60b1bad9884fba07f280c00316c05dbd8d5f6b86e01805e461aaf968
+  data.tar.gz: 73162b249b9676d13bdf015a7cba72949d3fe9834ff6b6441fbe452048613e04
 SHA512:
-  metadata.gz: 26ec66ace02ff31ced22d3bd331884c0c74d5ee7356e138897759ed70be2be7d52dca239d3f1ac30c6599c8133446d199db7833de18fda7053e6fc977a1bde3b
-  data.tar.gz: a60049ad709699ec112b43c6f281dd50ae6b80d3774c5c9a58e56d6daebcb5ccfc647544461f62f3f6e4a23367421d1401b34988ae22657764b72bf387c03ff8
+  metadata.gz: eb50e40c8eeb0873a68b1d84481391a1fa7b0c8f1971a461b662b86faa101bd3fd58a584f4364f2510e9df282904e3329f64b6319a16a684020b574f3aa0f1a1
+  data.tar.gz: 20f9e743881dca244716a5e14e97a34a050e07afb6ac954122988acf0cd7fd3b9bdf20c726ab73885c1a10301cc5ccdd194bcc38c50611340b6f77c06e87d2ab

data/CHANGELOG.md

@@ -1,3 +1,8 @@
+### [1.0.2] - 2026-02-09
+
+#### Changed
+- Made `PM.parse_string` a public class method so it can be called directly for parsing strings without file-based metadata enrichment.
+
 ### [1.0.1] - 2026-02-04
 
 #### Added

data/README.md

@@ -95,6 +95,14 @@ parsed = PM.parse("---\ntitle: Hello\n---\nContent here")
 
 When given a file path, `parse` adds `directory`, `name`, `created_at`, and `modified_at` to the metadata. Both forms run the full processing pipeline.
 
+Note that `PM.parse` treats single words (e.g. `'hello'`) as prompt IDs and appends `.md` to look them up as files. To parse a single word as literal string content, use `PM.parse_string`:
+
+```ruby
+PM.parse('hello')              #=> looks for hello.md in prompts_dir
+PM.parse_string('hello')       #=> parses "hello" as string content
+PM.parse_string('Any string')  #=> always parsed as content, never as a file
+```
+
 Given a file `code_review.md`:
 
 ```md

data/docs/api/pm-module.md

@@ -38,6 +38,44 @@ parsed = PM.parse("---\ntitle: Hello\n---\nContent")
 
 ---
 
+### PM.parse_string(string) → Parsed
+
+Parse a string directly through the processing pipeline, bypassing all file-detection logic. Unlike `PM.parse`, single words are never treated as prompt IDs.
+
+**Parameters:**
+
+| Name | Type | Description |
+|------|------|-------------|
+| `string` | String | Raw string content to parse |
+
+**Returns:** `PM::Parsed` (Struct with `metadata` and `content`)
+
+**Behavior:**
+
+- Always parses the input as string content — never looks up files
+- Runs the same pipeline as `PM.parse`: strip comments → extract YAML → shell expansion
+- Does not add `directory`, `name`, `created_at`, or `modified_at` to metadata
+
+```ruby
+# Single words are parsed as content, not treated as file basenames
+parsed = PM.parse_string('hello')
+parsed.content  #=> "hello"
+
+# Strings with YAML front-matter work as expected
+parsed = PM.parse_string("---\ntitle: Hello\n---\nContent")
+parsed.metadata.title  #=> "Hello"
+parsed.content         #=> "Content\n"
+```
+
+**When to use `parse_string` instead of `parse`:**
+
+```ruby
+PM.parse('summarize')          #=> looks for summarize.md
+PM.parse_string('summarize')   #=> parses "summarize" as content
+```
+
+---
+
 ## Configuration
 
 ### PM.config → Configuration

data/docs/getting-started/quick-start.md

@@ -40,6 +40,19 @@ puts parsed.to_s('name' => 'Alice')
 
 When parsing a file, PM also adds `directory`, `name`, `created_at`, and `modified_at` to the metadata.
 
+## Parse a String Directly
+
+`PM.parse` treats single words as prompt IDs and looks them up as files. To always parse a string as content, use `PM.parse_string`:
+
+```ruby
+PM.parse('hello')              #=> looks for hello.md in prompts_dir
+PM.parse_string('hello')       #=> parses "hello" as string content
+
+parsed = PM.parse_string("---\ntitle: Inline\n---\nSome content")
+parsed.metadata.title  #=> "Inline"
+parsed.content         #=> "Some content\n"
+```
+
 ## Parameters
 
 Parameters declared in the YAML front-matter define template variables:

data/docs/guides/parsing.md

@@ -69,6 +69,30 @@ String-parsed prompts do not have `directory`, `name`, `created_at`, or `modifie
 !!! warning "Include limitations"
     The `include` directive requires file context to resolve relative paths. It raises an error when used with string-parsed prompts.
 
+### PM.parse_string vs PM.parse
+
+Because `PM.parse` treats single words as prompt IDs (appending `.md` and looking them up as files), short strings like `"hello"` or `"summarize"` will trigger a file lookup instead of being parsed as content. Use `PM.parse_string` to always parse a string as content:
+
+```ruby
+# PM.parse treats single words as prompt IDs
+PM.parse('hello')          #=> looks for hello.md in prompts_dir
+PM.parse('summarize')      #=> looks for summarize.md in prompts_dir
+
+# PM.parse_string always parses as string content
+PM.parse_string('hello')          #=> Parsed with content "hello"
+PM.parse_string('summarize')      #=> Parsed with content "summarize"
+
+# Multi-word strings without .md extension work the same in both
+PM.parse("Hello world")           #=> Parsed with content "Hello world"
+PM.parse_string("Hello world")    #=> Parsed with content "Hello world"
+```
+
+Use `PM.parse_string` when:
+
+- Your input may be a single word that should not be treated as a file
+- You know the source is always a string, never a file path
+- You want to skip the file-detection logic entirely
+
 ## Metadata Extraction
 
 YAML front-matter is delimited by `---` fences:

data/lib/pm/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module PM
-  VERSION = '1.0.1'
+  VERSION = '1.0.2'
 end

data/lib/pm.rb

@@ -98,7 +98,7 @@ module PM
 
     Parsed.new(metadata: metadata, content: content)
   end
-  private_class_method :parse_string
+
 
   # Builds a Metadata object with defaults for shell and erb.
   def self.build_metadata(hash)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: prompt_manager
 version: !ruby/object:Gem::Version
-  version: 1.0.1
+  version: 1.0.2
 platform: ruby
 authors:
 - Dewayne VanHoozer
@@ -159,7 +159,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.5
+rubygems_version: 4.0.6
 specification_version: 4
 summary: Parse YAML metadata from markdown prompts with shell expansion and ERB rendering
 test_files: []