AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Work Pause

skill-mdproctor-cc-praxis-work-pause · by mdproctor

>

— No reviews yet
0 installs
34 views
0.0% view→install

Install

$ agentstack add skill-mdproctor-cc-praxis-work-pause

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-mdproctor-cc-praxis-work-pause)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
○ Archived

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Work Pause? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

work-pause

Commits all work-in-progress, pushes an entry onto the pause stack on workspace main, and switches both repos to their base branch. Supports multiple paused branches.

Uncommitted changes are always committed as a WIP: commit on the branch — no stash used. On resume, the WIP commit is reset so work continues cleanly.


Path Resolution (run first, always)

Run the bundled context script — no shell variable assignments, no CLAUDE.md scanning:

python3 ~/.claude/skills/project-init/ctx.py

Use WORKSPACE, PROJECT, BASE_BRANCH, CURRENT_BRANCH from the output as concrete strings. BASE_BRANCH defaults to main if not declared in the project CLAUDE.md.


Step 0 — Resolve paths

Read $PROJECT and $WORKSPACE from CLAUDE.md (see Path Resolution above).


Step 1 — Validate state

ls "$WORKSPACE/design/.meta" 2>/dev/null || { echo "No .meta found — not on a working branch."; exit 1; }
BRANCH_NAME=$(grep "^branch:" "$WORKSPACE/design/.meta" | sed 's/branch: //')
ISSUE_N=$(grep "^issue:" "$WORKSPACE/design/.meta" | sed 's/issue: //')

Must be on a branch where $WORKSPACE/design/.meta exists.


Step 2 — Commit WIP on project branch

PAUSE_TS=$(date -u +%Y-%m-%dT%H:%M:%SZ)
OUTPUT=$(python3 ~/.claude/skills/work-pause/pause_exec.py commit-wip "$PROJECT" message="WIP: paused $BRANCH_NAME at $PAUSE_TS")

Parse COMMITTED= from output:

  • COMMITTED=yes → WIP commit created
  • COMMITTED=clean → no commit needed (repo was clean)

Step 3 — Commit WIP on workspace branch

WS_OUTPUT=$(python3 ~/.claude/skills/work-pause/pause_exec.py commit-wip "$WORKSPACE" message="WIP: paused $BRANCH_NAME at $PAUSE_TS")

Parse COMMITTED= from output:

  • COMMITTED=yes → WIP commit created on workspace
  • COMMITTED=clean → workspace was clean

Step 4 — Push branches and add to pause stack

STACK_OUTPUT=$(python3 ~/.claude/skills/work-pause/pause_exec.py push-and-stack "$WORKSPACE" "$PROJECT" branch="$BRANCH_NAME" issue="$ISSUE_N" base-branch="$BASE_BRANCH")

Parse output:

  • PROJECT_PUSHED=yes|no — whether project branch push succeeded
  • WORKSPACE_PUSHED=yes|no — whether workspace branch push succeeded
  • STACKED=yes — pause entry added to stack on workspace main
  • If ERROR= appears, abort

This operation:

  1. Pushes both branches to origin (non-fatal if fails — WIP commits are local)
  2. Checks out base-branch in project, main in workspace
  3. Pulls latest from both remotes
  4. Adds pause entry to .pause-stack using stack.py
  5. Commits and pushes the stack change

If stack push to main fails: the script automatically aborts and pops the entry.


Step 5 — Parse stack depth and confirm

Get current stack depth:

STACK_DEPTH=$(python3 ~/.claude/skills/project-init/stack.py depth "$WORKSPACE/design/.pause-stack")

Display confirmation:

⏸  Paused:   Issue: #
   WIP committed: project=  workspace=
   Stack depth: 

You're on main — type work to resume this branch or start new work.

If stack depth > 3, add: ⚠️ Stack has paused branches — consider closing some.


Pause vs Wrap

work-pause is for switching branches mid-session — you're continuing to work, just on something else. It does not write HANDOFF.md or run the session wrap.

If the session is ending (not switching to other work), use handover (wrap) instead — it writes HANDOFF.md so the next session can resume on the same branch.

| Intent | Skill | |--------|-------| | Switch to a different branch now, come back later | work-pause | | End the session, continue this branch next time | handover (wrap) | | Branch is done, close everything | work-end |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.