# ops-long-task-repo-tracking-skill

- Repo URL: ssh://git@192.168.1.4:2222/qianliyun/ops-long-task-repo-tracking-skill.git
- Web URL: http://192.168.1.4:3000/qianliyun/ops-long-task-repo-tracking-skill
- Local path: /Users/bot1/.hermes/shared-skills/devops/long-task-repo-tracking
- Bot1 synced profiles: designer1, designer2, designer3, enterprise-consultant, finance, hr, it, legal, meow-chan, meow-fast, obsidian-bone, operations, queens-favorite, suwei-assistant, video, visual-operator
- Bot2 synced profiles: it2, kongkong, novelist, operator, screenwriter, storyboarder
- Machine/Profile: bot1/meow-chan coordinator; bot1+bot2 shared/profile skills
- Owner/Requester: studio robots
- Task type: Hermes skill / repository governance
- Status: active
- Last updated: 2026-05-28T18:54:31Z
- Latest branch/commit: main / 4454a23

## Purpose
Version-managed source for the shared Hermes `long-task-repo-tracking` skill. The skill tells robots when to load long-task governance, how to classify tasks, when to avoid unnecessary repositories, when durable source-of-truth/handoff work still requires repo tracking, and when long clear programmatic execution should be handed to Codex.

## Current authoritative description
The repo root `REPO_DESCRIPTION.md` is the source of truth for detailed evolving state.

## Latest maintenance note
User feedback: all robots should send longer, clearly specified, programmatic/execution-heavy tasks to Codex for the implementation portion. Version `1.2.1` adds a Codex execution delegation gate: the coordinating robot does prerequisite discovery, safety scoping, task brief, invocation, and verification; Codex performs bounded non-GUI implementation work such as code edits, scripts, build/test loops, deterministic file generation, HTML/CSS/JS implementation, data processing, package repair, and similar tool-heavy execution.

The rollout also updated `profile-delegation` to version `2.1.0` and all checked `codex` Skill copies to version `1.1.0` on bot1 and bot2 profiles.

This does not override safety boundaries: GUI/keyboard/mouse work still routes to `visual-operator`; NAS/shared-drive writes still follow NAS confirmation rules unless a standing exception applies; destructive commands, private account operations, payment/formal sends, permissions, profile/gateway/service changes, and ambiguous requirements require the governing safety workflow first.

Recent commits:
- 4454a23 docs: record codex delegation rollout
- 1ec15c3 docs: add codex execution delegation gate
- b37afc6 docs: lighten repository tracking gate and sync bot2 skill
- 1f6cb2e docs: relax repository creation gate

## Search keywords
AI Work, Git, Gitea, lumi_soul, repository mapping, long-task-repo-tracking, repo creation gate, one_off, local_tracking_optional, repo_required, repo_existing, handoff, durable deliverable, source-of-truth, Codex, programmatic execution, CODEX_TASK, bot1, bot2, it2, kongkong, novelist, operator, screenwriter, storyboarder, shared skill