session-control
The session-control skill manages session state transitions in /work environments by processing --resume and --fork command flags. It updates session.json and session.events.jsonl files to enable workflow resumption or branching. Use this exclusively for internal Claude Code workflow orchestration, not for user-facing session management, authentication, or application state handling.
git clone --depth 1 https://github.com/Chachamaru127/claude-code-harness /tmp/session-control && cp -r /tmp/session-control/opencode/skills/session-control ~/.claude/skills/session-controlSKILL.md
# Session Control Skill
/work の `--resume` / `--fork` フラグに応じてセッション状態を切り替える。
## 機能詳細
| 機能 | 詳細 |
|------|------|
| **セッション再開/分岐** | See [references/session-control.md](${CLAUDE_SKILL_DIR}/references/session-control.md) |
## 実行手順
1. workflow から渡された変数を確認
2. `scripts/session-control.sh` を適切な引数で実行
3. `session.json` と `session.events.jsonl` の更新を確認executor が返した advisor-request.v1 に対して方針だけ返す非実行 advisor
Browser automation through the repo agent-browser CLI. Explicit helper for navigation, forms, screenshots, scraping, and web-app checks. Prefer Browser Use or Playwright when available. Do NOT load for: sharing URLs, embedding links, or editing screenshot files.
Explicit helper for authentication and payment implementation with Clerk, Supabase Auth, or Stripe. Do NOT load for: general UI work, database design, or non-auth features.
Team execution mode — backward-compatible alias for harness-work with team orchestration. Composer/composer 2.5 maps to the cursor backend.
Validates brainstormed ideas with Cursor PM, updates Plans.md, then handoff back. Cursor ↔ Claude Code 2-Agent workflow support. Use when user mentions Cursor PM handoff, 2-agent plan validation, CC-Cursor round trip, or brainstorm review. Do NOT load for: implementation work, single-agent tasks, or direct coding.
Quality guardrail for Claude/Codex update integration. Detects doc-only Feature Table additions and requires implementation or explicit planning. Internal use only.
CI red? Call us. Pipeline fire brigade deploys. Use when user mentions CI failures, build errors, test failures, or pipeline issues. Do NOT load for: local builds, standard implementation work, reviews, or setup.
Explicit helper for CRUD scaffolding and API endpoint generation. Do NOT load for: UI components, form design, database schema discussion, or general implementation.