# Huacheng AI CLI Online Annotate

> Huacheng Ai Cli Online Annotate

- Skill: `tomevault-io/huacheng-ai-cli-online-annotate` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/huacheng-ai-cli-online-annotate`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/huacheng-ai-cli-online-annotate/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/huacheng-ai-cli-online-annotate

---


# /moonview:annotate — Annotation Processing

Process `.tmp-annotations.json` from the Plan panel. Supports 4 annotation types: Insert, Delete, Replace, Comment. Each is triaged for cross-impact and conflict before execution.

## Usage

```
/moonview:annotate <task_file_path> <annotation_file_path> [--silent]
```

## Annotation Types

| Type | Elements | Structure |
|------|----------|-----------|
| **Insert** | 3 | [context_before, insertion_content, context_after] |
| **Delete** | 3 | [context_before, selected_text, context_after] |
| **Replace** | 4 | [context_before, selected_text, replacement_content, context_after] |
| **Comment** | 4 | [context_before, selected_text, comment_content, context_after] |

> **See `references/annotation-processing.md`** for the full annotation file format, processing logic (triage rules, cross-impact assessment, conflict detection), and execution report format.

## Execution Steps

1. **Validate paths**: Both `task_file_path` and `annotation_file_path` must resolve (after symlink resolution) to a location under the project's `AiTasks/` directory. Reject with error if either path escapes `AiTasks/` (prevents path traversal via `..` or symlinks). Additionally, `annotation_file_path` basename must be `.tmp-annotations.json` — reject any other filename
2. **Read** the task file at the validated absolute path
3. **Read** `.index.json` — validate status is not `complete` or `cancelled`. If either, REJECT with error: tasks in terminal status cannot be modified
4. **Read** the annotation file (`.tmp-annotations.json`)
5. **Read** `.target.md` + `.plan.md` + `.test/` (latest criteria) for full context
6. **Parse** all annotation arrays
7. **Triage** each annotation by type and condition
8. **Assess** cross-impacts and conflicts against ALL files in the module
9. **Execute** changes per severity level
10. **Update** the task file with resolved changes and inline markers for pending items
11. **Update** `.index.json` in the task module:
    - Update `status` per State Transitions table: `draft`→`planning`, `review`/`executing`→`re-planning`, `blocked`→`planning`, others keep current
    - If the **new** status is `re-planning`, set `phase: needs-check`. For all other **new** statuses, clear `phase` to `""`
    - Update `updated` timestamp
12. **Write** `.summary.md` with condensed context reflecting annotation changes
13. **Clean up** the `.tmp-annotations.json` file (delete after processing)
14. **Git commit**: `-- ai-cli-task(<module>):annotate annotations processed`
15. **Write** `.auto-signal`: `{ "step": "annotate", "result": "(processed)", "next": "verify", "checkpoint": "post-plan", "timestamp": "..." }`
16. **Generate** execution report (print to screen or append to file per mode)

## State Transitions

| Current Status | After Annotate | Condition |
|----------------|---------------|-----------|
| `draft` | `planning` | First annotation processing |
| `planning` | `planning` | Additional annotations |
| `review` | `re-planning` | Revisions after assessment |
| `executing` | `re-planning` | Mid-execution changes |
| `re-planning` | `re-planning` | Further revisions |
| `blocked` | `planning` | Unblocking changes |
| `complete` | REJECT | Completed tasks cannot be modified |
| `cancelled` | REJECT | Cancelled tasks cannot be modified |

## Git

```
-- ai-cli-task(<module>):annotate annotations processed
```

## .auto-signal

| Result | Signal |
|--------|--------|
| Processed | `{ "step": "annotate", "result": "(processed)", "next": "verify", "checkpoint": "post-plan", "timestamp": "..." }` |

## Notes

- The `.tmp-annotations.json` is ephemeral — created by frontend, consumed and deleted by this skill
- Cross-impact assessment should check ALL files in the task module, not just the current file
- Comments add `> 💬`/`> 📝` blockquotes, never modify existing content
- **Content sanitization**: Before writing annotation content to task files, strip HTML comments (`<!-- ... -->`) and ANSI escape sequences to prevent hidden prompt injection. Preserve markdown formatting and visible text
- **Concurrency**: Annotate acquires `AiTasks/<module>/.lock` before proceeding and releases on completion (see Concurrency Protection in `commands/ai-cli-task.md`)

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/huacheng) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->