Skip to content

INTENT-2 v2: .prompt {{name}} substitution + .dialog dual-brace, drop comment exception#71

Merged
JarbasAl merged 1 commit into
devfrom
spec/intent-2-prompt-double-brace
Jun 26, 2026
Merged

INTENT-2 v2: .prompt {{name}} substitution + .dialog dual-brace, drop comment exception#71
JarbasAl merged 1 commit into
devfrom
spec/intent-2-prompt-double-brace

Conversation

@JarbasAl

Copy link
Copy Markdown
Member

What

Breaking reinterpretation of brace handling in .prompt and .dialog. The implementation already landed in ovos-spec-tools #38; this PR is the matching spec text.

Sections changed (intent-2.md)

  • §4.2 (.dialog) — flips the old "single-brace {name} only; no {{ }} form" restriction: .dialog now recognizes both {name} and {{name}} per OVOS-INTENT-1 §3.4, treating them identically.
  • §4.4 (.prompt):
    • The substitution variable is now {{name}} (double-brace only). A single {name}, a lone {/}, and literal JSON/markup ({}, { }, {"key": 1}) pass through unchanged. This is why prompts require double-brace — they routinely contain literal single braces.
    • The author-comment exception is removed entirely: a .prompt has no comment handling; <!-- … --> is literal text. The only special handling a .prompt receives is {{name}} substitution.
    • The prior fenced-code-block substitution rule is dropped (a single-brace {name} is already literal everywhere, so the carve-out is moot).
    • Worked example updated: {{query}} is substituted; the <!-- … --> line and single-brace {response} survive verbatim.
    • See-also line updated from {name} to {{name}}.
  • CHANGELOG.md — new OVOS-INTENT-2 ### 2 section describing the breaking .prompt/.dialog brace changes.
  • README.md — OVOS-INTENT-2 class column 12.

Version (triple-match)

Breaking (reinterprets previously-literal {{ }}; drops comment-stripping) → bump to Version 2:

  • header **Version:** 2
  • CHANGELOG ### 2 under OVOS-INTENT-2
  • README class column 2

Dangling-reference check

Removing the comment exception left no dangling references inside .prompt content. The only stale mention — the See-also "verbatim text with optional {name} substitution only" — was updated to {{name}}. The §3 common-reader #-comment rule is unrelated (it governs line-oriented files; .prompt is read whole and is explicitly exempt).

@coderabbitai

coderabbitai Bot commented Jun 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@JarbasAl, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 39 minutes and 9 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2c641d09-489a-4ca9-a539-1f1614243b94

📥 Commits

Reviewing files that changed from the base of the PR and between b7e16b9 and 384a426.

📒 Files selected for processing (3)
  • CHANGELOG.md
  • README.md
  • intent-2.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch spec/intent-2-prompt-double-brace

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

…rop comment exception

feat!: breaking reinterpretation of brace handling.

- §4.4 (.prompt): substitution variable is now {{name}} (double-brace) ONLY.
  A single {name}, a lone { or }, and literal JSON/markup pass through
  unchanged — which is why prompts (full of literal single braces) require
  double braces. The author-comment exception is removed entirely: a .prompt
  has no comment handling and <!-- --> is literal text. {{name}} substitution
  is the only special handling a .prompt receives.
- §4.2 (.dialog): now recognizes BOTH {name} and {{name}} per INTENT-1 §3.4,
  treating them identically.

Bumps OVOS-INTENT-2 to Version 2 (header, CHANGELOG ### 2, README class).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@JarbasAl JarbasAl force-pushed the spec/intent-2-prompt-double-brace branch from 9182345 to 384a426 Compare June 26, 2026 20:08
@JarbasAl JarbasAl marked this pull request as ready for review June 26, 2026 20:54
@JarbasAl JarbasAl merged commit 4fb8869 into dev Jun 26, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant