Claude-skill-registry-data lotar-task-tracking

Name: lotar-task-tracking
Author: majiayu000

Use this to create and maintain LoTaR tasks for work tracking, with minimal friction and consistent updates.

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry-data

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry-data "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/lotar-task-tracking" ~/.claude/skills/majiayu000-claude-skill-registry-data-lotar-task-tracking && rm -rf "$T"

manifest: data/lotar-task-tracking/SKILL.md

source content

Quick start

List tasks:
- ```
lotar list
```

Create a task:

lotar add "<title>" --priority=HIGH --type=feature

Update status:
- ```
lotar status <ID> in_progress
```

Add a short progress note:

lotar comment <ID> -m "what changed + where"

ID + project notes

IDs look like
```
PROJ-123
```
. If you’re in a single-project repo (or have
```
default_project
```
set), many commands accept numeric-only IDs.
When ambiguous, always use the fully-qualified ID or pass
```
--project
```
.

Good “agent” update pattern

Keep comments short and actionable:
- What changed (1 sentence)
- Where (paths/symbols)
- Next step (1 line)

Safety

Don’t paste secrets/PII into task comments (tokens, auth headers, cookies).