القائمة
DEPRECATED — merged into /full-finish. Use /full-finish instead.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Meta-Skill for auditing context-file hygiene. Two modes — Lite (~6.5K tokens, runs at session/task start) and Full (~150K tokens, runs on demand or weekly cron). Detects dual handoffs, version mismatches, broken cross-references, stale files, and contradictions. Master Plan §6.
Initialize Context Governance structure in a new project. Scaffolds all canonical files (CONTEXT-MANIFEST, PLAN, HANDOFF, MEMORY, CONVENTIONS, SCHEMAS-INDEX, GOTCHAS, OPEN-PROBLEMS) + CLAUDE.md governance section. Run once per project.
Universal post-task pipeline — multi-agent orchestrated audit, session handoff, docs, commit, build, release, deploy
Two-way WhatsApp communication — send progress updates and receive user replies via CC-Agent group
Open a GitHub Pull Request for review by a responsible agent (e.g., CODEX), wait for its response (text comment or 👍 reaction), remind it after 6 minutes with an @mention, and merge on approval — or after a 4-minute grace if no response. Use when the user asks to "send via PR for review", "open a PR and wait for <agent>", or to ship a reviewed change through the responsible-agent gate.
Start WhatsApp-to-Claude-Code bridge — polls CC-Agent GROUP every 60s for @cc/קלוד messages, processes as Claude Code tasks, replies in group
| name | end-session |
| description | DEPRECATED — merged into /full-finish. Use /full-finish instead. |
This skill has been merged into /full-finish (Phase 3.1 — Documentation & Handoff Agent).
Session handoff functionality (forensics, handoff document, memory extraction, WhatsApp notification) is now handled by the Documentation & Handoff Agent inside the /full-finish pipeline.
Use /full-finish instead. It runs the full release pipeline including session handoff.
If you ONLY need a session handoff without a release (no version bump, no EXE build, no GitHub release):
/live-state-orchestrator — the canonical engine for the PLAN.md / MEMORY.md / OPEN-PROBLEMS.md / HANDOFF.md lifecycle (active → consumed → archived). This is the SAME engine the Stop hook (end-session.sh) enforces before it allows a session to end./full-finish — it will detect "docs only" changes and skip QA/Security phases automatically (Phase 1 routing table), and runs /live-state-orchestrator internally (Part D).