Add include rules for short system prompt fragments

[Liyux3]

Summary

Several system prompt fragments in Claude Code's cli.js are under 500 characters and get filtered out by the minLength check in validateInput(). This means users cannot customize these prompts via tweakcc's system prompt editing feature.

These fragments come from:

• Doing Tasks section (rJ3 function): exploratory questions behavior, code comment policy, UI testing, prefer-editing rule, no-gold-plating rule
• Tone and Style section (HM3 function): emoji policy, concise output, colon-before-tool-calls rule
• Memory section: "What NOT to save in memory" guidelines

Changes

Added specific string-match include rules in validateInput(), following the same pattern already used for the security testing prompt (line 28-30). No changes to the filtering logic itself.

Test plan

• Run node tools/promptExtractor.js against Claude Code 2.1.126 binary and verify the newly included prompts appear in the output
• Check that no false positives are introduced (the matches are specific substring checks)

Summary by CodeRabbit

• Bug Fixes
  • Enhanced input validation to accept additional shorter prompt fragments from multiple content sections, improving flexibility in accepted input formats.

[coderabbitai]

📝 Walkthrough

Walkthrough

The validateInput function in tools/promptExtractor.js adds allowlist checks for specific short text snippets from prompt sections ("Doing tasks", "Tone and style", "What NOT to save"), enabling them to bypass minimum-length and heuristic rejection filters while preserving existing Git-status and system-reminder inclusion logic.

Changes

Prompt Validation Allowlist Enhancement

Layer / File(s)	Summary
Validation Allowlist Logic tools/promptExtractor.js	New text.includes and text.startsWith checks for whitelisted prompt fragments from "Doing tasks", "Tone and style", and "What NOT to save" sections are evaluated before length and heuristic filters to permit these short snippets as valid inputs.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Piebald-AI/tweakcc#341: Modifies validateInput with heuristic whitelist/blacklist checks for specific prompt text snippets in the same file.
• Piebald-AI/tweakcc#400: Updates promptExtractor.js to whitelist short system-reminder text that corresponds to prompt updates.

Suggested reviewers

• bl-ue

Poem

🐰 A rabbit hops through validation gates,
With whitelists that seal the fates,
Short snippets now dance free and light,
Bypassing filters left and right,
From "Doing tasks" to "What NOT save," 🎉
Validation's now a little brave.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and specifically describes the main change—adding include rules for short system prompt fragments—which directly matches the core objective of the PR to enable extraction of previously filtered-out short prompt sections.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

tools/promptExtractor.js (1)

32-47: ⚡ Quick win

Use section separators instead of new prose comments

Line 32, Line 40, and Line 45 add new prose comments. This conflicts with the repo rule to avoid adding comments unless explicitly requested. If grouping is needed, use the // ====== style section separator instead.

As per coding guidelines, "Do not add comments unless explicitly requested" and "Use // ====== lines for major code sections".

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tools/promptExtractor.js` around lines 32 - 47, The added prose comments
before the short-prompt blocks violate the repo rule; replace those freeform
comments with section separator lines (e.g., // ====== Short prompts from the
"Doing tasks" section) rather than prose, keeping the existing conditional
checks on the text variable (the blocks related to rJ3 and HM3 in cli.js and the
"What NOT to save" memory checks) intact and without extra sentences.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@tools/promptExtractor.js`:
- Line 38: Replace the double-quoted string in the conditional using
text.startsWith with a single-quoted literal and escape the internal apostrophe
so it conforms to the project's Prettier style; specifically update the
expression text.startsWith("Don't add features, refactor") to use single quotes
and an escaped apostrophe (i.e., text.startsWith('Don\'t add features,
refactor')) in tools/promptExtractor.js where the startsWith check is performed.

---

Nitpick comments:
In `@tools/promptExtractor.js`:
- Around line 32-47: The added prose comments before the short-prompt blocks
violate the repo rule; replace those freeform comments with section separator
lines (e.g., // ====== Short prompts from the "Doing tasks" section) rather than
prose, keeping the existing conditional checks on the text variable (the blocks
related to rJ3 and HM3 in cli.js and the "What NOT to save" memory checks)
intact and without extra sentences.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 076d89c0-fe08-499f-92b8-c8384c4f3615

📥 Commits

Reviewing files that changed from the base of the PR and between 8a6ea7a and cfbc35f.

📒 Files selected for processing (1)

• tools/promptExtractor.js