feat: clear context after building implementation plan

[dotuananh0712]

Summary

• Adds context clearing step after generating detailed implementation plan
• Frees up memory for implementation and debugging

Fixes #478

Summary by CodeRabbit

• Documentation
  • Added guidance recommending developers clear context during implementation phases to free up available memory capacity, enabling more efficient debugging and development work
  • Added clarification that git diff commands must be executed separately without chaining them together to ensure effective code review processes

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds procedural guidance to two skills: a new step to clear context before implementing plans to optimize available memory, and clarification that git diff commands must be executed separately without chaining operators.

Changes

Cohort / File(s)	Summary
Execution Plan Skill skills/executing-plans/SKILL.md	Adds Step 1 item 5 "Clear context" with guidance to clear the context window before implementation to free up memory for debugging and execution.
Code Review Skill skills/requesting-code-review/code-reviewer.md	Adds guidance blocks emphasizing that git diff commands must be run separately without chaining with && operator, including explicit warnings against command chaining.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• Add problem-solving skills from amplifier patterns #1: Modifies skills/executing-plans/SKILL.md with related changes to execution flow guidance and step organization.

Poem

🐰 With memory cleared and context bright,
Claude Code runs with all its might!
And git commands, separated clean,
Make review workflows lean and keen!
These skills now guide with wisdom's light ✨

🚥 Pre-merge checks | ✅ 5 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Out of Scope Changes check	⚠️ Warning	The code-reviewer.md changes about git diff command chaining relate to issue #476, not the main objective #478, making them out of scope for this pull request.	Remove the code-reviewer.md changes or create a separate pull request for issue #476 to maintain clear scope separation.

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: adding a context-clearing step after building an implementation plan.
Linked Issues check	✅ Passed	The pull request implements the core requirement from issue #478: automatically clearing context after plan generation to free memory for implementation and debugging.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

🤖 Fix all issues with AI agents

In `@skills/executing-plans/SKILL.md`:
- Around line 23-25: The "Clear context" bullet is ambiguous and
self-referential—replace the line "Tell Claude Code to clear its context/window"
with one of two explicit options and document which is intended: either (A) an
autonomous instruction for the agent (e.g., "Claude Code: clear your
context/window to free memory") if the agent can perform it, or (B) a
user-facing request (e.g., "Ask the user to clear the context/window to free
memory") if manual action is required; also add the specific command or method
name to use (or state "no automatic command available") and update the
header/description for the "Clear context" section so it clearly states whether
clearing is automatic or requires user intervention.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Clarify the self-referential instruction and mechanism.

The phrasing "Tell Claude Code to clear its context/window" creates confusion because if Claude Code is executing this skill, it's being instructed to tell itself to do something. Additionally, the mechanism for clearing context is not specified—there's no command, method, or user action described.

Consider clarifying:

• Direct instruction: "Clear your context/window to free up memory" (if this is an action Claude Code can perform autonomously)
• User action: "Request the user to clear the context window" (if this requires manual user intervention)
• Specific command: Reference the actual command or method if one exists

The PR objectives mention "automatically clear context," but this instruction appears manual and ambiguous.

📝 Proposed clarification

If context clearing requires user action:

-5. **Clear context** to free up memory for implementation:
-   - Tell Claude Code to clear its context/window
-   - This ensures more memory available during implementation and debugging
+5. **Clear context** to free up memory for implementation:
+   - Request the user to clear the context window
+   - This frees up memory for implementation and debugging

If context clearing is autonomous:

-5. **Clear context** to free up memory for implementation:
-   - Tell Claude Code to clear its context/window
-   - This ensures more memory available during implementation and debugging
+5. **Clear context** to free up memory for implementation:
+   - Clear your context window now
+   - This frees up memory for implementation and debugging

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	5. **Clear context** to free up memory for implementation:
	- Tell Claude Code to clear its context/window
	- This ensures more memory available during implementation and debugging
	5. **Clear context** to free up memory for implementation:
	- Request the user to clear the context window
	- This frees up memory for implementation and debugging

Suggested change

	5. **Clear context** to free up memory for implementation:
	- Tell Claude Code to clear its context/window
	- This ensures more memory available during implementation and debugging
	5. **Clear context** to free up memory for implementation:
	- Clear your context window now
	- This frees up memory for implementation and debugging

🤖 Prompt for AI Agents

In `@skills/executing-plans/SKILL.md` around lines 23 - 25, The "Clear context"
bullet is ambiguous and self-referential—replace the line "Tell Claude Code to
clear its context/window" with one of two explicit options and document which is
intended: either (A) an autonomous instruction for the agent (e.g., "Claude
Code: clear your context/window to free memory") if the agent can perform it, or
(B) a user-facing request (e.g., "Ask the user to clear the context/window to
free memory") if manual action is required; also add the specific command or
method name to use (or state "no automatic command available") and update the
header/description for the "Clear context" section so it clearly states whether
clearing is automatic or requires user intervention.