Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions skills/executing-plans/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,9 @@ Load plan, review critically, execute tasks in batches, report for review betwee
2. Review critically - identify any questions or concerns about the plan
3. If concerns: Raise them with your human partner before starting
4. If no concerns: Create TodoWrite and proceed
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
Comment on lines +23 to +25
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ 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.


### Step 2: Execute Batch
**Default: First 3 tasks**
Expand Down
7 changes: 7 additions & 0 deletions skills/requesting-code-review/code-reviewer.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,11 +22,18 @@ You are reviewing code changes for production readiness.
**Base:** {BASE_SHA}
**Head:** {HEAD_SHA}

**IMPORTANT: Run these commands SEPARATELY, not chained with &&:**
```bash
git diff --stat {BASE_SHA}..{HEAD_SHA}
```

Then run:
```bash
git diff {BASE_SHA}..{HEAD_SHA}
```

**NEVER chain commands with &&** - this causes consent prompts and makes debugging harder. Always use separate Bash calls.

## Review Checklist

**Code Quality:**
Expand Down