Simplified document review methodology with 4 core tags (@FIX, @TODO, @VERIFY, @OK) and [MACRO] flag for systemic impact. Use for annotating and reviewing documentation.
Reviews documentation using 4 core tags and [MACRO] flag to annotate changes and analyze systemic impacts.
/plugin marketplace add theflysurfer/claude-skills-marketplace/plugin install theflysurfer-claude-skills-marketplace@theflysurfer/claude-skills-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Version: 2.0 (Simplified)
Philosophy: 4 core tags + 1 flag = maximum clarity, minimum confusion
| Tag | Hotstring | Usage | Examples |
|---|---|---|---|
<!-- @FIX: --> | ;fix | Correct factual error | Typo, incorrect formula, false info |
<!-- @TODO: --> | ;tod | Add/modify content (generic) | Rephrase, add example, complete section |
<!-- @VERIFY: --> | ;ver | Verify against sources | Check formula, test link, cross-check data |
<!-- @OK: --> | ;okk | Light validation | Section read, no obvious issue |
| Tag | Hotstring | Usage | Context |
|---|---|---|---|
[MACRO] | ;mac | Systemic impact flag | Add AFTER description if macro change |
<!-- @LOCKED: --> | ;lck | Lock content | Forbid modification during session |
<!-- @APPROVED: --> | ;app | Formal validation | NEVER modify unless explicit request |
Default: Any tag = MICRO change (local, no systemic impact)
If systemic impact: Add [MACRO] AFTER the description
<!-- @FIX: Incorrect Amount formula [MACRO] affects 3 databases -->
<!-- @TODO: Rename field [MACRO] verify all references -->
<!-- @VERIFY: Workflow change [MACRO] test 4 user roles -->
| Trigger | Example | Why MACRO |
|---|---|---|
| Modified formula/calc | Change formula used elsewhere | Calculation propagation |
| Rename field/variable | Rename "Budget" → "Allocation" | Multiple references |
| Workflow/process | Add "Cancelled" state | Rights/validations impact |
| Cross-system relation | Modify DB1 → DB2 link | Referential integrity |
| External API/sync | Test sync with ERP | External regression risk |
<!-- @FIX: Typo "budjet" → "budget" -->
<!-- @TODO: Rephrase - Section too technical for non-expert -->
<!-- @TODO: Example - Add typical contract amount -->
<!-- @VERIFY: Formula - Check against JSON source -->
<!-- @FIX: Formula Amount = A21*A23 incorrect [MACRO] should be if(A20="Manual",A21,A23), affects Budget Remaining in 3 files -->
<!-- @TODO: Rename "Budget Remaining" → "Budget Available" [MACRO] check 3 databases + API sync -->
<!-- @VERIFY: Workflow add state "Cancelled" [MACRO] test impact on 4 user roles + reporting -->
.md file;fix Typo "budjet" → "budget";tod Rephrase - Too technical;fix Incorrect formula ;mac;okk Glossary section"Parse comments from [folder/file]"
"Generate comment tracking report"
"Process all @FIX from [folder]"
.md scan, tag extraction[MACRO] flag → Impact analysis required@VERIFY → Check sources[MACRO] → detailed report generation@OK and @APPROVED: KEPT with date only<!-- @OK: 2025-10-21 --> or <!-- @APPROVED: 2025-10-21 -->@LOCKED never modified@APPROVED modified only on explicit request## Comment Processing Report - [Date]
### Statistics
- Total: 15 comments
- @FIX: 3 (including 1 [MACRO]) | @TODO: 8 (including 2 [MACRO])
- @VERIFY: 3 | @OK: 1
### By file
- file1.md: 6 (2 MACRO)
- file2.md: 5 (1 MACRO)
- file3.md: 4 (0 MACRO)
### By priority
#### High priority (@FIX + [MACRO])
1. **@FIX [MACRO]** - `file.md:L34`
**Before**: Formula Amount = A21*A23
**After**: if(A20="Manual",A21,A23)
**Impact**: 3 files use this result
**Tests**: Verify calculations in file2, file5, file7
**Action**: Edit L34 + cross-check
#### Medium (@TODO)
2. **@TODO** - `file.md:L12`
**Action**: Add typical amount example
**Impact**: Local
#### Low (@VERIFY simple)
3. **@VERIFY** - `file.md:L67`
**Action**: Check formula against JSON
**Result**: Confirmed correct
| Old Tag | New Equivalent |
|---|---|
@CLARIFY | @TODO: Rephrase - [description] |
@MISSING | @TODO: Add - [description] |
@ADD-EXAMPLE | @TODO: Example - [description] |
@SUGGEST | @TODO: Suggestion - [description] |
@QUESTION | @TODO: Question - [description] |
@NOTE | @TODO: Note - [description] |
@CHECK-FORMULA | @VERIFY: Formula - [description] |
@CHECK-LINK | @VERIFY: Link - [description] |
@METHODOLOGY | @TODO: Methodology - [description] |
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.