timewarrior-efficient-entry

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Efficient Time Entry with Timewarrior

借助Timewarrior实现高效时间记录

Fast, consistent time tracking: avoid tag chaos, time guessing, and duplicate entries through a proven 5-step workflow.

快速、一致的时间追踪：通过经过验证的5步工作流，避免标签混乱、时间预估错误和重复记录。

When to Use This Skill

何时使用此方法

✅ You need to log work quickly but want consistency by Friday
✅ You're backfilling yesterday/last week but can't remember exact times
✅ You have gaps in your week and need to fill them with accurate tags
✅ You're tired and might create duplicate tag names

✅ 你需要快速记录工作，但希望到周五时记录保持一致
✅ 你需要补录昨天/上周的记录，但记不清具体时间
✅ 你的周记录存在空白，需要用准确的标签填补
✅ 你感到疲惫，可能会创建重复的标签名称

When NOT to Use This Skill

何时不使用此方法

❌ You're doing real-time tracking (just
```
timew start
```
as you work)
❌ You need detailed historical reconciliation (use full reference docs)
❌ You're analyzing trends (use analysis reports)

❌ 你正在进行实时追踪（工作时直接使用
```
timew start
```
即可）
❌ 你需要详细的历史对账（使用完整参考文档）
❌ 你正在分析趋势（使用分析报告）

The Core Problem

核心问题

Without discipline, agents under time pressure:

Skip tag discovery →
```
dev
```
,
```
development
```
,
```
DEV
```
all in use by Friday
Invent times → backfilled data doesn't match actual patterns
Create placeholder tags →
```
buffer
```
,
```
misc
```
,
```
admin
```
pollute the list
Guess-and-fix later → tag mismatches discovered hours later
Leave unmeasured gaps → incomplete daily totals

缺乏规范时，处于时间压力下的用户会出现以下问题：

跳过标签查询 → 到周五时
```
dev
```
、
```
development
```
、
```
DEV
```
同时存在
随意编造时间 → 补录的数据与实际模式不符
创建占位标签 →
```
buffer
```
、
```
misc
```
、
```
admin
```
这类标签会污染标签列表
先猜测后修正 → 数小时后才发现标签不匹配
留下未统计的空白 → 每日总记录不完整

The 5-Step Efficient Entry Workflow

5步高效记录工作流

Step 1: Query Existing Tags BEFORE Entering New Data

步骤1：在录入新数据前先查询现有标签

bash

timew tags :week

Why: Takes 5 seconds. Prevents tag name chaos. You'll see exactly what tags you've been using.

What you do: Note the exact spelling, case, and format (e.g.,

development

not

dev

bash

timew tags :week

原因： 仅需5秒，可避免标签名称混乱。你能清楚看到自己一直在使用的标签。

操作： 注意标签的准确拼写、大小写和格式（例如：使用

development

而非

dev

）。

Step 2: For Rapid Same-Day Entry, Copy Tags from Recent Work

步骤2：快速录入当日记录时，复制近期工作的标签

Scenario: You have 5 minutes before a meeting. Log 3 activities today.

bash

undefined

场景： 会议前你有5分钟时间，需要记录今天的3项活动。

bash

undefined

Find exact tag names from similar recent work

从近期类似工作中查找准确的标签名称

timew export :day | grep -o '"tags":[[^]]*]' | head -5

Then use those EXACT names when entering new entries

录入新记录时使用这些完全一致的标签名称

timew start 9am development project-alpha timew stop timew start 11am code-review team-beta


**Key:** You're reusing proven tag names, not inventing new ones.

timew start 9am development project-alpha timew stop timew start 11am code-review team-beta


**关键：** 复用已确认的标签名称，而非创建新标签。

Step 3: For Backfill (Yesterday/Last Week), Query the Pattern Day

步骤3：补录（昨天/上周）记录时，查询参考日的模式

Scenario: You forgot to log yesterday. You need times AND tags.

bash

undefined

场景： 你忘记记录昨天的工作，需要补录时间和标签。

bash

undefined

Check a similar day from this week for both times and tags

查询本周某一个类似工作日的时间和标签模式

timew report 2025-01-18 rc.columns=start,end,tags

Then match that pattern for yesterday

参照该模式补录昨天的记录

timew track 2025-01-19T09:00:00 - 2025-01-19T12:00:00 development project-alpha timew track 2025-01-19T13:00:00 - 2025-01-19T17:00:00 development project-alpha


**Key:** You're matching existing patterns, not guessing new times. If you
can't remember exact times, use the anchors you DO remember (meeting times,
when you left).

timew track 2025-01-19T09:00:00 - 2025-01-19T12:00:00 development project-alpha timew track 2025-01-19T13:00:00 - 2025-01-19T17:00:00 development project-alpha


**关键：** 参照现有模式，而非猜测新时间。如果记不清具体时间，使用你记得的锚点（如会议时间、下班时间）。

Step 4: Fill Gaps ONLY with Existing Tags (No Placeholders)

步骤4：仅使用现有标签填补空白（不使用占位标签）

Scenario: Your week has gaps between logged sessions.

bash

undefined

场景： 你的周记录中已录入的时段之间存在空白。

bash

undefined

Check which tags dominated the day

查看当天占比最高的标签

timew summary :day monday

Fill gaps > 30 min using tags from that day only

仅使用当天的标签填补超过30分钟的空白

timew track 12:00 - 14:00 development # Gap after morning dev timew track 11:00 - 13:00 project-alpha # Gap with context from work

timew track 12:00 - 14:00 development # 上午开发后的空白 timew track 11:00 - 13:00 project-alpha # 结合工作背景填补空白

Skip gaps < 30 min (context-switching overhead not worth tracking)

忽略30分钟以内的空白（切换上下文的成本不值得统计）


**Key:** Never create `buffer`, `context-switch`, or `admin` tags.
Reuse what you know.


**关键：** 切勿创建`buffer`、`context-switch`或`admin`这类标签，仅复用已有的标签。

Step 5: Bulk Verify Before Friday EOD

步骤5：周五下班前批量验证

bash

undefined

bash

undefined

See all tags you've used this week

查看本周使用的所有标签

timew tags :week

Look for duplicates, typos, variations

查找重复、拼写错误和变体

(e.g., "dev" vs "development", "alpha" vs "project-alpha")

（例如："dev" vs "development"，"alpha" vs "project-alpha"）

Check for placeholder tags you forgot about

检查是否有遗忘的占位标签

timew summary :week


**Fix discovered duplicates:**

```bash

timew summary :week


**修正发现的重复标签：**

```bash

Find all entries with misspelled tag

查找所有包含拼写错误标签的记录

timew export :week | grep -o '"dev"'

Modify entries to use correct tag

修改记录以使用正确的标签

timew tag @5 development timew untag @5 dev

undefined

timew tag @5 development timew untag @5 dev

undefined

Quick Reference: The Workflow Matrix

快速参考：工作流矩阵

Scenario	Step 1	Step 2	Step 3	Step 4
Rapid same-day entry	Query tags (5s)	Copy recent tags	—	—
Backfill yesterday	Query tags (5s)	—	Query pattern day	Verify consistency
Fill week gaps	Query tags (5s)	—	—	Fill with existing tags only
Friday verification	`timew tags :week`	—	—	Check for duplicates

场景	步骤1	步骤2	步骤3	步骤4
快速录入当日记录	查询标签（5秒）	复制近期标签	—	—
补录昨天的记录	查询标签（5秒）	—	查询参考日模式	验证一致性
填补周记录空白	查询标签（5秒）	—	—	仅使用现有标签填补
周五验证	`timew tags :week`	—	—	检查重复项

Common Mistakes (And How the Workflow Prevents Them)

常见错误（以及工作流如何避免它们）

Mistake	Why It Happens	Workflow Fix
`dev` + `development` coexist	Skip Step 1 (tag query)	Always query first
Backfilled times are ±2 hours off	Invent times (Step 3)	Query a pattern day instead
`buffer` , `misc` pollute tags	Create placeholders (Step 4)	Reuse only existing tags
Discover duplicates Friday PM	Guess-and-fix approach	Do Step 5: bulk verify
Gaps in daily totals	Skip filling (Step 4)	Fill gaps > 30min only

错误	产生原因	工作流解决方案
`dev` 和 `development` 同时存在	跳过步骤1（标签查询）	始终先查询标签
补录的时间误差超过±2小时	随意编造时间（步骤3）	改为查询参考日模式
`buffer` 、 `misc` 污染标签列表	创建占位标签（步骤4）	仅复用现有标签
周五下午才发现重复标签	采用先猜测后修正的方式	执行步骤5：批量验证
每日总记录存在空白	跳过填补步骤（步骤4）	仅填补超过30分钟的空白

When Each Step Takes Under 1 Minute

每个步骤耗时均不超过1分钟

Step 1 (Query tags): 5 seconds →
```
timew tags :week
```
Step 2 (Copy tags): 10 seconds →
```
timew export :day | grep tags
```
Step 3 (Query pattern): 10 seconds →
```
timew report SIMILAR_DAY
```
Step 4 (Fill gaps): 30 seconds → 3-4
```
timew track
```
commands
Step 5 (Verify): 20 seconds →
```
timew tags :week
```
and scan for typos

Total for a complete backfill + gap fill: ~2 minutes instead of 10+ minutes of guessing and fixing.

步骤1（查询标签）： 5秒 →
```
timew tags :week
```
步骤2（复制标签）： 10秒 →
```
timew export :day | grep tags
```
步骤3（查询参考模式）： 10秒 →
```
timew report SIMILAR_DAY
```
步骤4（填补空白）： 30秒 → 3-4条
```
timew track
```
命令
步骤5（验证）： 20秒 →
```
timew tags :week
```
并检查拼写错误

补录记录+填补空白的总耗时： 约2分钟，而非10分钟以上的猜测和修正时间。

References

参考资料

For detailed commands and advanced operations, see:

```
entry-patterns.md
```
– Step-by-step commands for each scenario
```
tag-management.md
```
– List, filter, and color-code tags
```
data-correction.md
```
– Modify, delete, undo operations
```
analysis-reports.md
```
– Query and reporting commands
```
complete-reference.md
```
– Full timewarrior command reference

如需详细命令和高级操作，请查看：

```
entry-patterns.md
```
– 各场景的分步命令
```
tag-management.md
```
– 标签的列出、筛选和颜色编码
```
data-correction.md
```
– 修改、删除、撤销操作
```
analysis-reports.md
```
– 查询和报告命令
```
complete-reference.md
```
– Timewarrior完整命令参考