You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- document {{TASK_HEADER_PATTERNS}} in CLAUDE.md and README.md variable lists
- update CLAUDE.md 'Plan format' key pattern to reflect configurable headers
and the removal of the package-level taskHeaderPattern regex
- rename TestDefaultPatternsMatchLegacyRegex and rewrite its comment to be
honest: the template-driven compiler is stricter than the legacy regex
about whitespace, so the test only covers canonical inputs
- exclude gosec G704 (SSRF taint) in *_test.go files; false positive on
httptest server URLs in pkg/web/watcher_test.go
Copy file name to clipboardExpand all lines: CLAUDE.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ docs/plans/ # plan files location
61
61
62
62
## Key Patterns
63
63
64
-
- Plan format: Checkboxes (`- [ ]` / `- [x]`) belong only in Task sections (`### Task N:` or `### Iteration N:`). The `Task` / `Iteration` keywords are structural tokens matched by `pkg/plan/parse.go` (`taskHeaderPattern`) and MUST stay in English even when plan content is written in another language — task titles and body text may be localized, but the section header keyword is fixed. Success criteria, Overview, and Context should not use checkboxes — they cause extra loop iterations. The task prompt handles them when present, but plan authors should avoid them.
64
+
- Plan format: Checkboxes (`- [ ]` / `- [x]`) belong only in Task sections. By default, headers matching `### Task {N}: {title}` or `### Iteration {N}: {title}` are recognized; the `Task` / `Iteration` keywords are structural tokens and MUST stay in English even when plan content is written in another language — task titles and body text may be localized, but the default section header keywords are fixed. Recognized header shapes are configurable via `task_header_patterns` (compiled by `pkg/plan/patterns.go`, passed to `pkg/plan/parse.go``ParsePlan`/`ParsePlanFile` as a variadic `patterns ...string`; empty falls back to `plan.DefaultTaskHeaderPatterns`). Success criteria, Overview, and Context should not use checkboxes — they cause extra loop iterations. The task prompt handles them when present, but plan authors should avoid them.
- Plan creation signals: QUESTION (with JSON payload) and PLAN_READY
67
67
- Streaming output with timestamps
@@ -373,6 +373,7 @@ Implementation:
373
373
-`{{DEFAULT_BRANCH}}` - detected default branch (main, master, origin/main, etc.), overridable via `--base-ref` CLI flag or `default_branch` config option
374
374
-`{{DIFF_INSTRUCTION}}` - git diff command for current iteration (first: `git diff main...HEAD`, subsequent: `git diff`)
375
375
-`{{PREVIOUS_REVIEW_CONTEXT}}` - previous review context block for external review iterations (empty on first iteration, formatted context on subsequent)
376
+
-`{{TASK_HEADER_PATTERNS}}` - quoted, `or`-joined list of configured `task_header_patterns` templates (used in `task.txt`)
376
377
-`{{agent:name}}` - expands to Task tool instructions for the named agent
377
378
378
379
Variables are also expanded inside agent content, so custom agents can use `{{DEFAULT_BRANCH}}` etc.
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -692,6 +692,7 @@ Custom prompt files support variable expansion. All variables use the `{{VARIABL
692
692
|`{{PROGRESS_FILE}}`| Path to the progress log file |`.ralphex/progress/progress-feature.txt`|
693
693
|`{{GOAL}}`| Human-readable goal description |`implementation of plan at docs/plans/feature.md`|
694
694
|`{{DEFAULT_BRANCH}}`| Default branch name (overridable via `--base-ref` or `default_branch` config) |`main`, `master`, `origin/main`|
695
+
|`{{TASK_HEADER_PATTERNS}}`| Quoted, `or`-joined list of configured `task_header_patterns` templates (used in `task.txt`) |`'### Task {N}: {title}' or '### Iteration {N}: {title}'`|
695
696
|`{{agent:name}}`| Expands to Task tool instructions for the named agent | (see below) |
0 commit comments