القائمة
Manage the user's Vicinae Todo List from the terminal. Use when the user mentions todos, tasks, reminders, or when noting persistent cross-session work items.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | vicinae-todo |
| description | Manage the user's Vicinae Todo List from the terminal. Use when the user mentions todos, tasks, reminders, or when noting persistent cross-session work items. |
Syncs with the Vicinae launcher's Todo List extension.
File: ~/.local/share/vicinae/support/store.raycast.todo-list/todo.json
Sections: pinned, todo, completed. Vicinae reads on launch; edits appear next open.
T="python3 ~/.agents/skills/vicinae-todo/scripts/manage.py"
All mutating commands accept a selector: a 0-based index OR a case-insensitive title substring. Substring auto-searches across sections (narrow with -s). Ambiguous matches print candidates and exit non-zero.
$T list # all sections
$T list -s todo --json # JSON output, one section
$T add "Task A" "Task B" # batch add
$T add "Deploy" --pin -t ops -p 3 -d tomorrow
# --due: YYYY-MM-DD | +Nd | today | tomorrow | weekday name
$T done "deploy" # match by title substring
$T done 0 # or by index
$T undo 0 # completed -> todo
$T pin "task a" # todo -> pinned
$T unpin 0 # pinned -> todo
$T edit "task b" "Updated title" # rename
$T rm "old item" # delete (any section)
$T clear # wipe completed
Item fields: title, completed, timeAdded (ms), tag? (#foo), priority? (1=low 2=mid 3=high), dueDate? (ms).
Open in launcher: vicinae 'vicinae://launch/store.raycast.todo-list/index'
Full PR review workflows -- first-pass, deeper (overcoverage), follow-up (re-review). Load when the user invokes /review-pr or explicitly asks for a PR review, deeper wave, or re-review; never ambiently.
Shared atom for analyzing a diff and writing a structured PR description. Background knowledge for workflow commands -- not invoked directly.
Author a publication-grade single-file HTML design doc (RFCs, architecture proposals, sync prep). Editorial typography, decision cards, fact-checked code references, Playwright-verified layout, secret-gist publishing. Use when an engineer asks for a design doc, RFC, monograph, sync-prep brief, or "make this look like a real spec."
Shared atom for running quality checks, committing, and pushing. Background knowledge for workflow commands -- not invoked directly.
Self-review your aggregate diff before shipping to catch dead weight, junk code, perf misses, pattern drift, AI slop, and scope creep. Use when the user asks to scrub, stranger-review, or clean up changes prior to opening a PR.
Shared atom for structural maintainability judgment on a diff -- hunt code-judo simplifications, spaghetti-condition growth, file-size explosions, and orchestration smells. Background knowledge for review and self-review flows -- not invoked directly.