sync-ops-knowledge

Sync Ops Knowledge

ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of metadata.changelog above — e.g. sync-ops-knowledge vX.Y — recent: <summary>. Then proceed.

Review recent changes in a managed codebase and update the ops agent's documentation to reflect new operational requirements. Ensures the agent stays current without modifying application code.

---

Use Case

An ops agent manages a service it doesn't control — it can't modify the source code, but it needs to know:

• New environment variables that must be configured on deploy
• Changed API endpoints that health checks or scripts rely on
• New Docker services or removed services
• Schema migrations that affect backup/restore procedures
• New configuration options the agent should advise on

This skill reviews git history and proposes documentation updates.

---

Prerequisites

# Path to the managed codebase (read-only — never modify)
MANAGED_REPO=${MANAGED_REPO:-""}  # e.g. ~/app or a local clone

# Optional: days of history to review (default: 7)
SINCE_DAYS=${SINCE_DAYS:-7}

Or SSH-based review of a remote repo:

SSH_HOST=${SSH_HOST:-""}
SSH_USER=${SSH_USER:-"ubuntu"}
SSH_KEY=${SSH_KEY:-"~/.ssh/id_rsa"}
APP_PATH=${APP_PATH:-"~/app"}
RUN="ssh -i $SSH_KEY $SSH_USER@$SSH_HOST"

Parse $ARGUMENTS for --since=Nd or a repo path.

---

Step 1: Get Recent Commits

Local repo:

cd $MANAGED_REPO
git log --oneline --since="${SINCE_DAYS} days ago" | head -50

Remote repo:

$RUN "cd $APP_PATH && git log --oneline --since='${SINCE_DAYS} days ago' | head -50"

Display commit list to user. If no commits in the window, say so and exit.

---

Step 2: Analyze Each Commit for Ops Impact

For each commit, check what files changed:

# Local
git show --stat [commit-hash]

# Remote
$RUN "cd $APP_PATH && git show --stat [commit-hash]"

Flag commits that touch ops-relevant files: