Claude Skill

cancel-jeffy

Use when the user runs /cancel-jeffy to stop the active Jeffy improvement loop in the current project

LLM Mart · 0 points · 1 views 153 listing impressions 0 install-command copies
Download lenamonj-jeffy-loop-skills_cancel-jeffy-866fd18.zip · 0 KB

Install

skills CLI npx skills add https://github.com/lenamonj/jeffy-loop/tree/main/skills/cancel-jeffy
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install lenamonj-jeffy-loop@llmmart
Git git clone https://github.com/lenamonj/jeffy-loop.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole lenamonj/jeffy-loop collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Cancel Jeffy

Stop the Jeffy loop in this project by removing the loop state file the Stop hook reads.

  1. Project root is the directory Claude Code was started in, not wherever the shell currently sits: the Bash tool's cwd persists across calls and may have drifted into a subdirectory that holds its own orphaned state file from another session. Always check state files with absolute paths anchored at the project root, never bare relative ones.
  2. Check <project-root>/.claude/jeffy-loop.local.md. If it exists, read its frontmatter and report its session_id, iteration, and started_at, then delete the file, and <project-root>/.claude/jeffy-loop.local.md.refused beside it when that sidecar exists (the Stop hook writes it after refusing a state file whose frontmatter opener is not exactly ---), and confirm the loop is cancelled. Once the file is gone the Stop hook lets the session end normally.
  3. Also check <project-root>/.claude/ralph-loop.local.md: it belongs to the ralph-loop plugin's engine or a pre-2.0 Jeffy. If it exists, report the same frontmatter fields and delete it too, so no legacy loop keeps re-feeding.
  4. If neither file exists, report that no Jeffy loop is active in this project and stop.
  5. Remind the user that PLAN.md, BACKLOG.md, and JOURNAL.md are untouched: the loop picks up where it left off the next time they run /jeffy.
Files (jeffy-loop)
  • SKILL.md 1.5 KB
    ---
    name: cancel-jeffy
    description: Use when the user runs /cancel-jeffy to stop the active Jeffy improvement loop in the current project
    disable-model-invocation: true
    ---
    
    # Cancel Jeffy
    
    Stop the Jeffy loop in this project by removing the loop state file the Stop hook reads.
    
    1. Project root is the directory Claude Code was started in, not wherever the shell currently sits: the Bash tool's cwd persists across calls and may have drifted into a subdirectory that holds its own orphaned state file from another session. Always check state files with absolute paths anchored at the project root, never bare relative ones.
    2. Check `<project-root>/.claude/jeffy-loop.local.md`. If it exists, read its frontmatter and report its session_id, iteration, and started_at, then delete the file, and `<project-root>/.claude/jeffy-loop.local.md.refused` beside it when that sidecar exists (the Stop hook writes it after refusing a state file whose frontmatter opener is not exactly `---`), and confirm the loop is cancelled. Once the file is gone the Stop hook lets the session end normally.
    3. Also check `<project-root>/.claude/ralph-loop.local.md`: it belongs to the ralph-loop plugin's engine or a pre-2.0 Jeffy. If it exists, report the same frontmatter fields and delete it too, so no legacy loop keeps re-feeding.
    4. If neither file exists, report that no Jeffy loop is active in this project and stop.
    5. Remind the user that PLAN.md, BACKLOG.md, and JOURNAL.md are untouched: the loop picks up where it left off the next time they run /jeffy.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.