← ClaudeAtlas

log-timelisted

Generate a paste-ready time-log for Redmine (or any tracker the user's config describes) by cross-checking the evidence sources the user configured — calendar events, task-tracker activity, Claude Code session history, meeting transcripts, spreadsheets, or any custom source. Behavior (sources, target tickets, day rules, output format) comes from the free-form config at ~/.claude/log-time/config.md; the skill itself makes no assumptions about working hours or which sources exist. Use ANY time the user wants to log time, prep daily/weekly tracker entries, reconstruct what they did on past dates, batch-fill timesheets, or asks "what was I working on between X and Y" with the intent of logging hours. Trigger on phrases like "/log-time", "log my time", "log time", "time log", "redmine entries", "timesheet", "fill in my hours". Evidence-only output with confidence ratings; read-only against every source.
SashaMarchuk/claude-plugins · ★ 0 · AI & Automation · score 75

Install: claude install-skill SashaMarchuk/claude-plugins

# /log-time — Universal time-log builder You are helping the user reconstruct what they actually worked on across past days and turn it into paste-ready time-tracker entries (Redmine by default — any tracker their config describes). The skill supplies the *mechanics* — preflight, parallel evidence gathering, synthesis, allocation, emit. The user's config supplies every *rule* — which sources to check, which tickets to log against, how a day should add up, and what an entry looks like. This is an accuracy-over-speed workflow. Cross-reference everything, flag uncertainty, never pad. ## Operating principles 1. **Evidence first.** Every emitted entry traces back to something a source actually shows. Never invent work, never fabricate hours, never silently fill gaps. 2. **The config is the contract.** `~/.claude/log-time/config.md` is free-form markdown written by the user (or the onboarding wizard). Read it top to bottom and treat it as instructions: its sources, ticket targets, day rules, skip rules, and output style override every default in this file. 3. **No assumed daily target.** The skill has no built-in notion of how many hours a day "should" contain. Without a target in config, output is evidenced-only — a day may total 3.25h and that is correct output. A target exists only if the user's config declares one or the user states one for this run. 4. **Use whatever tools the user has.** Each source is satisfied by any working method — MCP tool, CLI, local files, a spread