hermes-task-framework 1.0.3__tar.gz → 1.2.0__tar.gz

{hermes_task_framework-1.0.3 → hermes_task_framework-1.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hermes-task-framework
-Version: 1.0.3
+Version: 1.2.0
 Summary: Structured task management skills for Hermes Agent — task creation, decomposition, stage gates
 Project-URL: Source, https://github.com/nuffin/hermes-task-framework-pip
 Requires-Python: >=3.11

{hermes_task_framework-1.0.3/task-framework → hermes_task_framework-1.2.0/hermes_task_framework}/skills/task-external-repos-pattern/SKILL.md

@@ -1,10 +1,31 @@
 ---
-name: task-external-repos-pattern
-description: "Documentation for the repos/ directory pattern — cloning external git repos into a task for analysis, audit, or code extraction. Defines cleanup semantics, directory structure, and pitfall avoidance."
 author: Hermes Agent
-license: MIT
 category: software-development
-tags: [task, repos, git, clone, analysis, external]
+description: Documentation for the repos/ directory pattern — cloning external git
+  repos into a task for analysis, audit, or code extraction. Defines cleanup semantics,
+  directory structure, and pitfall avoidance.
+license: MIT
+metadata:
+  hermes:
+    scenes:
+    - research
+    - coding
+    tags:
+    - git
+    - repos
+    - clone
+    - analysis
+    - audit
+    - task
+    - software-development
+name: task-external-repos-pattern
+tags:
+- task
+- repos
+- git
+- clone
+- analysis
+- external
 version: 1.0.0
 ---
 
@@ -109,23 +130,19 @@ This pattern extends the `task-framework` skill's directory structure. The `task
 
 For `task_reset --hard` semantics: `repos/` is never deleted by cleanup operations (same as `input/`). Custom `clean.sh` scripts can further refine which directories to protect.
 
-## Kanban Escalation: Multi-Repo Tasks → Kanban
-
-When a task involves **multiple independent external repos** (e.g. cloning 5+ repos from an awesome-list for study), the work typically decomposes into parallel workstreams. The user's convention is **one kanban card per task-framework task** (not one card per sub-operation):
+## Optional: Escalate to External Task Manager
 
-User signal: *"一个 clone 任务创建一个 card"* / *"这是多个任务了，放到 default 看板里"*
+When a task involves **multiple independent external repos** (e.g. cloning 5+ repos from an awesome-list for study), the work typically decomposes into parallel workstreams. The recommended convention is **one tracking card per task-framework task** (not one card per sub-operation):
 
 **Right approach:**
 1. Create a single task-framework task with its own `repos/` directory
-2. Create one kanban card for that task, `--workspace dir:<task-path>`
-3. Update the bridge db.yaml to map task hash ↔ card id
+2. If using an external task manager (kanban board, issue tracker, etc.), create one card/issue for that task and link it via the task hash
+3. Map the external card ID back to `.hermes-task.json` if your workflow requires bidirectional linking
 
 **Wrong approach:**
-- Creating one kanban card per individual sub-repo
+- Creating one tracking card per individual sub-repo
 - Mixing unrelated work into one card
 
-See also: `kanban-orchestrator` skill for decomposition playbook, `kanban-bridge` for task ↔ card mapping.
-
 ## Custom Clean Methods (Implemented)
 
 Each task can protect sensitive directories from cleanup via a `scripts/clean.sh` script:
@@ -157,9 +174,9 @@ echo "[clean] output/ cleaned"
 - 没有 clean.sh 时回退到默认行为，不破坏现有任务
 
 **本 task 的 clean.sh 示例路径：**
-`tasks/20260615-213922.awesome-obsidian-vaults-cc6b3b/scripts/clean.sh`
+`tasks/<ts>.<task-name>-<hash6>/scripts/clean.sh`
 该脚本保护 `repos/`、`input/`，只清理 `output/`。
 
 **Framework 集成状态：**
-- `task-framework` SKILL.md 已更新，记录了 clean.sh 查找顺序和模板（`~/hermes/skills/software-development/task-framework/SKILL.md` 的 Task Directory Structure 章节）
+- `task-framework` SKILL.md 已更新，记录了 clean.sh 查找顺序和模板
 - `analysis` task-type 生命周期文档也加了自定义清理的提示

{hermes_task_framework-1.0.3/task-framework → hermes_task_framework-1.2.0/hermes_task_framework}/skills/task-framework/CHANGELOG.md

@@ -1,10 +1,40 @@
 # Changelog — task-framework
 
+## 2026-08-06 (v1.1.0)
+
+### feat: manage_task.py — 6 new lifecycle commands
+- `create` — directory + hash + meta + templates + optional inbox move
+- `accept` — create task from inbox file/dir (auto-derives name)
+- `decline` — move inbox item to declined/ with DECLINED.md
+- `status` — update ## Status line + auto index update
+- `view` — print README.md + TASK.md (hash/dir/name resolution)
+- `reset` — clear output/ + reset checkboxes + set status active (--no-hard for soft reset)
+- All commands use cp+verify+rm for file moves (never raw mv)
+- All commands auto-run update-index.py after changes
+
+### fix: code quality (A1-A4, B1/B4/B6, C2/C3/C6)
+- A1: replace 4 stale ~/.hermes/skills/ hardcoded paths with relative scripts/ paths
+- A2: cmd_init .hermes-task.json schema 5→12 fields (matches cmd_create)
+- A3: unify three index systems — reindex calls update-index.py, list scans dirs directly
+- A4: task-runner.sh log path logs/ → output/logs/ (matches task_reset cleanup scope)
+- B1: hash6() uses secrets.token_hex(3) instead of md5(random) across all 3 scripts
+- B4: _safe_move_file/_safe_move_dir rollback on failure (clean dst, preserve src)
+- B6: cmd_decline uses os.path.basename() to prevent path injection
+- C2: remove stale "Skill 文件结构一览" section (listed 3 scripts, actually 5)
+- C3: add .gitignore, remove tracked __pycache__/*.pyc
+- C6: unify env var resolution — all 3 scripts share _resolve_tasks_root() (HERMES_TASKS_ROOT | HERMES_TASKS_DIR → profile config → global config → fallback)
+
+### docs: SKILL.md updates (D1-D5)
+- D1: trigger signal section uses manage_task.py create instead of ad-hoc bash
+- D3: update create_task.py reference to manage_task.py create
+- D4: Named Outputs uses task_ref.set_output() instead of inline python -c
+- D5: resolve_ref/check_cycles reference scripts/task_ref.py instead of inline code
+
 ## 2026-06-06
 
 - feat: hash-based task_view — search by hash, name glob fallback (92b838d)
 - feat: scripts layout — task-runner.sh, task_ref.py with ref: resolution + cycle detection (92b838d)
-- feat: TASK_MEMORY.md template — per-task memory with append-only log format (92b838d, 435f85d)
+- feat: CHANGELOG.md template — per-task memory with append-only log format (92b838d, 435f85d)
 - fix: browser-screen-record-task scripts/ path alignment (927124f)
 - feat: venv management — auto uv venv + pip install per task (927124f)