vibe-log-cli

🥈Silver

A CLI tool for logging and analyzing Claude Code and Cursor ai-driven coding sessions. Generates productivity reports for developers and managers. Integrates with local development environments and project management tools.

284170Updated Today

Intermediate30min to implementautomation

Saves ~45 min per use

Quick InstallView Source

git clone https://github.com/vibe-log/vibe-log-cli.git

Works with:

Claude

Overview

About This Skill

Setup & Installation

Quick Install

No install command available. Check the GitHub repository for manual installation instructions.

Alternative Install (Git Clone)

git clone https://github.com/vibe-log/vibe-log-cli

Requirements

Claude Code or compatible AI agent
Works with: Claude

Quick Start Guide

Install the Skill

Copy the install command above and run it in your terminal.

Open Your AI Agent

Launch Claude Code, Cursor, or your preferred AI coding agent.

Try It Out

Use the prompt template or examples below to test the skill.

Customize

Adapt the skill to your specific use case and workflow.

Usage Examples

Prompt Template

I'm using vibe-log-cli to analyze my coding sessions with [AI_TOOL]. Here's the data from my last [NUMBER] sessions: [DATA]. Can you help me identify patterns, productivity trends, or areas for improvement?

Example Output

## Coding Session Analysis for [USERNAME]

### Key Metrics:
- **Total Sessions Analyzed**: 15
- **Average Session Duration**: 42 minutes
- **Most Active Time**: 2:00 PM - 4:00 PM

### Productivity Trends:
- **High Productivity Days**: Tuesdays and Thursdays
- **Low Productivity Days**: Fridays

### AI Tool Usage:
- **Most Used AI Tool**: Cursor (75% of sessions)
- **Most Common Commands**: 'Explain code', 'Debug', 'Optimize'

### Recommendations:
- Schedule coding sessions for Tuesdays and Thursdays
- Avoid starting sessions on Fridays
- Focus on improving debugging skills based on frequent use of 'Debug' command