skills/issue-tracking/SKILL.md
Suggest or manage Trekker tracking when the user talks about bugs, features, backlog items, or work that should survive this session.
npx skillsauth add obsfx/trekker-codex issue-trackingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when the conversation shifts from discussion into tracked work.
trekker search "pagination" --type task,subtask --limit 5
trekker search "cursor" --type task,subtask --limit 5
Use single keywords. Trekker search is full-text, not semantic.
trekker task create -t "Fix pagination cursor regression" -d "Investigate duplicate results in cursor pagination under filtered list view." -p 1
trekker comment add TREK-14 -a "codex" -c "Checkpoint: reproduced duplicate results when sorting by updated_at."
If Trekker is not initialized in the current workspace, ask before running trekker init.
development
Use Trekker as the persistent source of truth for tracked work in Codex. Search first, restore context, work one task at a time, and close tasks with summary comments.
development
Keep Trekker as the source of truth while using Codex session planning as a temporary mirror.
documentation
Work through Trekker tasks autonomously by recovering context, selecting ready work, documenting progress, and finishing with clean summaries.
testing
Start tracked work the right way: search first, restore task context, check dependencies, then mark the task in progress.