auto-tag

Generate pomodoro session tags and notes from recent git context.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/c3z/agent-pomodoro --skill auto-tag-c3z
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-tag
Source: https://github.com/c3z/agent-pomodoro/tree/main/.claude/skills/auto-tag
Command: npx skills add https://github.com/c3z/agent-pomodoro --skill auto-tag-c3z

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual work of naming and categorizing pomodoro sessions after you finish, so your focus history stays accurate and useful without extra effort.

Core Features & Use Cases

  • Git-Aware Tagging: Inspects recent diffs and commit messages to infer what kind of work you just completed.
  • Fixed Tag Vocabulary: Converts changes into consistent tags such as backend, frontend, tests, docs, config, feature, and fix.
  • Session Notes Generation: Summarizes the work into a concise note that can be attached when stopping the session.
  • Fallback Behavior: If there are no git changes, it uses conversation context to produce reasonable tags and notes.
  • Use Case: After a coding sprint, the skill can automatically label the session as frontend, tests, and refactor, then stop the timer with a clear summary.

Quick Start

Ask the assistant to end the current pomodoro session and generate tags and a short note from the most recent git activity.

Frequently Asked Questions about auto-tag

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically generate pomodoro session tags from git commits?

You can automatically generate pomodoro session tags by reading recent git diffs and commit history, mapping changes to a fixed vocabulary like backend, frontend, or tests, then stopping the session with those tags applied.

What is git context tagging for focus sessions?

Git context tagging inspects recent code diffs and commit messages to infer work types, categorizing focus sessions into consistent tags such as docs, config, feature, or refactor.

How do I categorize work blocks based on recent code changes?

Categorize work blocks by analyzing git diffs and commit history, then mapping detected modifications to predefined tags like backend, frontend, or tests to ensure consistent session categorization.

Can I stop a pomodoro timer with an auto-generated git summary?

Yes, you can stop a pomodoro timer with an auto-generated git summary by calling apom stop with concise session notes and tags derived from recent git activity.

What happens to workflow automation tagging if there are no git changes?

If there are no git changes, workflow automation tagging falls back to conversation context to produce reasonable tags and notes for the completed pomodoro session.