Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From waymark
<!-- tldr ::: guide interactive waymark addition to files with proper syntax -->
npx claudepluginhub outfitter-dev/waymarkHow this command is triggered — by the user, by Claude, or both
Slash command
/waymark:addagents/commands/The summary Claude sees in its command listing — used to decide when to auto-load this command
<!-- tldr ::: guide interactive waymark addition to files with proper syntax --> # Add Waymark Command Guide the user through adding a waymark to a file. ## Arguments - `$1` - File path (required) - `$2` - Marker type (optional: tldr, todo, fix, note, about, etc.) ## Context Injection Target file: !`[ -f "$1" ] && cat "$1" | head -100 || echo "File: $1 (will be created)"` Existing waymarks: !`[ -f "$1" ] && (wm find "$1" --text 2>/dev/null || rg ':::' "$1" -n) || echo "No existing waymarks"` ## Instructions Load the `using-waymarks` skill for grammar and marker guidance. ### Step 1...
/plannotator-annotateOpens interactive annotation UI for a specified markdown file or folder using plannotator annotate command.
/noteCapture a note to your brain using the `brain add` command, appending to today's daily file by default. Supports --file for specific files and --ref for code references.
/qimplRuns autonomous implementation session guided by a markdown work file, tracking progress in the file while enforcing strict context window limits and code quality rules.
/addInjects externally-sourced findings into the most recent /adamsreview:review artifact for this branch. Validates via Phase 4, re-renders, and re-publishes. Supports paste or structured --file --line --claim args.
Share bugs, ideas, or general feedback.
Guide the user through adding a waymark to a file.
$1 - File path (required)$2 - Marker type (optional: tldr, todo, fix, note, about, etc.)Target file: ![ -f "$1" ] && cat "$1" | head -100 || echo "File: $1 (will be created)"
Existing waymarks: ![ -f "$1" ] && (wm find "$1" --text 2>/dev/null || rg ':::' "$1" -n) || echo "No existing waymarks"
Load the using-waymarks skill for grammar and marker guidance.
If file path provided:
tldr :::If no file path:
If marker type provided ($2), use it.
Otherwise, use AskUserQuestion to determine intent:
tldrtodofixnoteaboutwarnBased on marker type:
For tldr:
#docs for documentation)For about:
For todo/fix:
@agent, @alice)For note/warn:
Determine correct insertion point:
tldr → After shebang/frontmatter, before codeabout → Line above target constructUse Edit tool to insert the waymark with proper comment syntax for the file type.
If wm CLI available, prefer:
wm add $1 --type <marker> --content "<content>" --line <line>
Show the user the inserted waymark and surrounding context for confirmation.