Skip to content

Narrow crush-code activation to explicit invocation only - #8

Merged
Skeyelab merged 3 commits into
mainfrom
fix/crush-code-activation-trigger
May 23, 2026
Merged

Skeyelab merged 3 commits into
mainfrom
fix/crush-code-activation-trigger

Conversation

@Skeyelab

Copy link
Copy Markdown
Member

Summary

  • Prevent accidental activation from generic phrases like "get to work", "keep going", or "work the issues"
  • Require explicit /crush-code or "run crush-code" to trigger the skill

Test plan

  • Verify skill no longer activates on casual "keep going" / "get to work" prompts

Skeyelab added 3 commits May 15, 2026 01:40
Prevent accidental activation from generic phrases like "get to work",
"keep going", or "work the issues" — require explicit /crush-code or
"run crush-code".

Assisted-by: Crush:claude-sonnet-4-5
When telegram_send_message is not available, fall back to stdout for
status messages and stdin prompts for blocking questions.

Assisted-by: Crush:claude-sonnet-4-5
Across tdd, diagnose, crush-code, and improve-codebase-architecture:
- Only make the smallest change needed
- Every change must be traceable to a specific requirement
- Do not test or guard against impossible/unreachable states

Assisted-by: Crush:claude-sonnet-4-5
@Skeyelab
Skeyelab merged commit bfa89c4 into main May 23, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant