Log Auto

Automatically log completed work from orchestrated tasks to external project management tools like Linear, Jira, GitHub Issues, or Obsidian.

When to Use This Command

Run this command when...

• You have finished a task and want to automatically push completion data to your project management tool
• You need to synchronize work done in Claude with external tracking systems without manual copy-paste
• A sprint is ending and you want to batch-log multiple completed tasks to your team tracking board
• You want to maintain an audit trail of what was built, when, and how long it took
• You need standup-ready work logs generated from actual task completion data

Quick Start

Copy
# .claude/commands/log-auto.md
---
name: Log Auto
description: Auto-log work to external project management tools
command: true
---
Log work for: $ARGUMENTS

Detect connected PM tools and push task completion data including:
- Task description and status
- Files modified and lines changed
- Time spent and completion timestamp
- Related commits and branches

Copy
# Invoke the command
claude "/log-auto TASK-017 to Linear"

# Expected output
# > Detecting connected tools... Found: Linear (API key configured)
# > Gathering task data for TASK-017...
# >   Status: completed
# >   Files: 4 modified, 1 created
# >   Commits: 3 (abc1234, def5678, ghi9012)
# >   Duration: ~45 minutes
# > Logging to Linear issue FE-234...
# > Successfully updated Linear with completion data

Core Concepts

Concept	Description
Tool Detection	Automatically discovers configured PM tools via API keys and config files
Task Data Collection	Gathers completion metrics from git history, file diffs, and orchestration state
Format Adaptation	Transforms log data into the format expected by each target tool
Bidirectional Linking	Creates cross-references between Claude tasks and external issue IDs
Batch Logging	Supports logging multiple tasks in a single invocation for sprint boundaries

Log Auto Data Flow
===================

  Task Completion
       |
       v
  +------------+     +-------------+     +-----------+
  | Collect    | --> | Transform   | --> | Push      |
  | Metrics    |     | Format      |     | To Tool   |
  +------------+     +-------------+     +-----------+
       |                   |                   |
  Git commits         Tool-specific       Linear API
  File changes        formatting          Jira API
  Time tracking       Field mapping       GitHub API
  Status data         Template apply      Obsidian md

Configuration

Parameter	Description	Default	Example	Required
$ARGUMENTS	Task ID and optional target tool	current task	"TASK-017 to Linear"	No
target_tool	Project management tool to log to	auto-detect	"linear", "jira", "github"	No
include_diff	Attach code diff summary to the log entry	false	true	No
log_format	Template for the log entry content	tool default	"standup", "detailed"	No
batch	Log all completed tasks since last sync	false	true	No

Best Practices

1. Configure API keys in environment -- Set LINEAR_API_KEY, JIRA_TOKEN, or GITHUB_TOKEN in your shell environment or .env file so auto-detection works seamlessly.

2. Use task IDs consistently -- Reference the same task identifiers across Claude orchestration and your PM tool to enable bidirectional linking and accurate status sync.

3. Log at natural boundaries -- Invoke after completing a feature, fixing a bug, or finishing a sprint rather than after every small change to keep logs meaningful.

4. Review before batch logging -- When using batch: true, preview the collected data first with --dry-run to ensure no draft or incomplete tasks get pushed to your PM tool.

5. Customize log templates per team -- Create team-specific log formats that include the fields your standup or retrospective process requires.

Common Issues

API authentication failures: Token expiration or incorrect scopes cause push failures. Verify your API key has write permissions and has not expired. For Linear, ensure the key has "Issues: Write" scope.

Task ID mismatch: If Claude internal task ID does not map to an external issue, the log cannot be linked. Use explicit mapping: "/log-auto TASK-017 as LINEAR-FE-234" to create the association.

Duplicate log entries: Running log-auto multiple times for the same task creates duplicate entries in some tools. Check for existing entries before logging, or use --update mode to upsert instead of insert.