القائمة
Use when the user wants to check the ELIGIA stack for outdated components (Docker, Python, git repos, npm) and apply safe updates with healthcheck rollback.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | check-updates |
| description | Use when the user wants to check the ELIGIA stack for outdated components (Docker, Python, git repos, npm) and apply safe updates with healthcheck rollback. |
| model | sonnet |
| allowed-tools | Bash |
Checks all ELIGIA stack components for updates and applies safe ones.
ONEDRIVE_PATH="${ONEDRIVE_PATH:-$OneDrive}"
ELIGIA_DIR="${ELIGIA_DIR:-C:/EligIA}"
SCRIPT="${ONEDRIVE_PATH}/.eligia/stack/scripts/check-updates.py"
Verify $SCRIPT exists. If not, print error and stop.
python "$SCRIPT" --apply --json --save 2>&1
Capture the JSON output. If the command fails, retry without --apply (dry-run fallback).
Parse the JSON output and generate a WhatsApp-friendly summary:
🔄 *Stack Update Report — YYYY-MM-DD*
🐳 *Docker*
✅ atlassian-marlink — al día
⬆️ hindsight — actualizado (abc123→def456)
📦 *Python*
✅ litellm 1.83.3
⬆️ fastmcp 3.2.0 → 3.2.1
pip install --upgrade fastmcp
🗂️ *Git Repos*
⬆️ paperclip-mcp — 3 commits disponibles
🖥️ *Desktop*
⬆️ skills-manager.exe — nueva versión disponible
https://github.com/xingkongliang/skills-manager/releases/latest
🤖 *Hermes*
⚠️ 69 commits de retraso
hermes update && repair-hermes-windows.ps1
📋 *npm*
ℹ️ trello-mcp latest: 1.1.0
Only include components with status != up_to_date in the summary.
If everything is up to date, send: ✅ Todo el stack está al día.
$ARGUMENTS
Mine architecture decision records (ADRs), gotcha files, runbooks, and docs/archive for cross-project lessons that warrant ai-playbook canonical specs. Use when a project lacks a populated retros/ directory but has equivalent material in other forms.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Orchestrate the canonical task↔PR↔release flow end-to-end. Two modes — `/dev-flow start <description>` scaffolds an OpenSpec change + branch + (optional) worktree + git hook ready for commits; `/dev-flow ship` validates the current branch + pushes + opens PR + monitors CI. Use whenever you start any non-trivial change in a playbook-consuming project. LLM-agnostic — works for Claude Code, Cursor, Antigravity, Gemini CLI, OpenCode, and humans.
Implement an OpenSpec change in parallel using multiple subagents (one per disjoint task group inside the same slice). Use when the slice's tasks.md has ≥2 task groups with disjoint write-paths AND >30 min of parallelisable work. For sequential implementation use openspec-apply-change instead.
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"