ctx-pause
Pause context hooks for this session. Use when context nudges aren't needed for the current task.
Best use case
ctx-pause is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Pause context hooks for this session. Use when context nudges aren't needed for the current task.
Teams using ctx-pause should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ctx-pause/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ctx-pause Compares
| Feature / Agent | ctx-pause | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Pause context hooks for this session. Use when context nudges aren't needed for the current task.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Pause all context nudge and reminder hooks for the current session. Security hooks (dangerous command blocking) still fire. ## When to Use - User says "pause ctx", "pause context", "quiet mode" - User says "stop the nudges", "too many reminders" - Quick investigation or one-off task that doesn't need ceremonies - User explicitly asks to reduce context overhead ## When NOT to Use - User wants to silence a specific hook (use `ctx hook message edit` to customize or silence individual hooks) - User wants to permanently disable hooks (edit `.claude/settings.local.json`) - Session involves real project work that benefits from persistence nudges ## Execution Run the pause command: ```bash ctx hook pause ``` Then confirm to the user: > Context hooks paused for this session. Nudges, reminders, and ceremony > prompts are silenced. Security hooks still fire. > > Resume anytime with `/ctx-resume`. ## Important Notes - **Session-scoped**: only affects the current session, not other terminals - **Hooks still fire silently**: they check the pause flag and no-op - **Graduated reminder**: a minimal `ctx:paused` indicator appears in hook output so the state is never invisible - **Resume before wrap-up**: if the session evolves into real work, resume hooks before wrapping up to capture learnings and decisions - **Initial context load is unaffected**: the ~8k token startup injection happens before any command runs: pause only affects subsequent hooks
Related Skills
ctx-verify
Verify before claiming completion. Use before saying work is done, tests pass, or builds succeed.
ctx-skill-creator
Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.
ctx-sanitize-permissions
Audit tool permissions for dangerous or overly broad entries. Use to ensure safe agent configuration.
ctx-recall
Browse session history. Use when referencing past discussions or finding context from previous work.
ctx-prompt
Apply, list, and manage saved prompt templates from .context/prompts/. Use when the user asks to apply, list, or create a reusable template like code-review or refactor.
ctx-journal-normalize
Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.
ctx-import-plans
Import plan files into project specs directory. Use to convert external plans into project-tracked specs.
ctx-compact
Archive completed tasks and trim context. Use when context files are growing large.
ctx-check-links
Audit docs for dead links. Use before releases, after restructuring docs, or when running a documentation audit.
ctx-add-task
Add a task. Use when follow-up work is identified or when breaking down complex work into subtasks.
ctx-add-learning
Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.
ctx-add-decision
Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.