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.

312170Updated 4d ago

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

How to Use

1. **Installation:** Run `npm install -g vibe-log-cli` or `pip install vibe-log-cli` depending on your environment. Verify installation with `vibe-log --version`. 2. **Start Logging:** Begin your coding session with `vibe-log start --session "[SESSION_NAME]"`. This creates a session file in `~/.vibe-logs/` that tracks all IDE interactions. 3. **Analyze Session:** After your session, run `vibe-log analyze --session "[SESSION_NAME]" --date-range "[START_DATE]-[END_DATE]"` to generate reports. Use `--export-json` to get raw data for custom analysis. 4. **Share Insights:** Generate team reports with `vibe-log report --team "[TEAM_NAME]" --period "[TIME_PERIOD]"` and share via `--share [EMAIL]` or `--export-pdf`. 5. **Integrate with Tools:** Connect to project management tools using `vibe-log integrate --tool jira` or `--tool github`. This syncs session data with your existing workflows. Tips: - Use consistent session naming (e.g., "feature-x-implementation") for better tracking - Run `vibe-log optimize --dry-run` weekly to get AI-driven suggestions for improving your coding sessions - For pair programming sessions, use `vibe-log start --collaborators "[NAME1],[NAME2]"` to track joint productivity

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

Use vibe-log-cli to analyze my recent [CODING_SESSION_NAME] session from [START_DATE] to [END_DATE]. Generate a productivity report highlighting: 1) Total time spent coding, 2) Most active files modified, 3) Frequency of ai-assisted completions, 4) Time spent in different IDE modes (editing vs. reviewing), and 5) Key metrics for my [TEAM_NAME] dashboard. Include recommendations for optimizing future sessions based on the patterns observed.

Example Output

### Vibe-Log CLI Productivity Report
**Session:** Full-Stack E-Commerce Refactor (2024-05-15 to 2024-05-17)
**Total Duration:** 14 hours 22 minutes

#### Key Metrics:
- **AI-Assisted Completions:** 187 (62% of all code changes)
  - Top AI Suggestions: React component optimizations (34 times), API endpoint refactoring (22 times), TypeScript type improvements (18 times)
- **Most Active Files:** 
  1. `src/components/ProductCard.tsx` (8 modifications, 4.2 hours)
  2. `src/hooks/useCart.ts` (6 modifications, 3.8 hours)
  3. `src/pages/Checkout.tsx` (5 modifications, 2.9 hours)
- **IDE Mode Distribution:**
  - Editing Mode: 68% (9h 43m)
  - Review Mode: 22% (3h 11m)
  - Debugging Mode: 10% (1h 28m)

#### Team Dashboard Metrics:
- **Code Churn:** 24% (below team average of 31%)
- **AI Dependency:** 0.82 completions per minute (team average: 0.65)
- **Focus Time:** 71% (above team average of 63%)

#### Recommendations:
1. **Optimize AI Prompts:** The high frequency of React component suggestions suggests your prompt templates could be more specific about state management patterns.
2. **Reduce Context Switching:** The 22% time in review mode indicates potential for better pre-commit hooks to catch issues earlier.
3. **Leverage AI for Testing:** Only 3 AI completions involved test files (1.6%). Consider adding test generation to your AI workflow.

#### Next Steps:
- Run `vibe-log-cli --export-json` to get raw data for deeper analysis
- Share this report with your team lead using `vibe-log-cli --share team-lead@company.com`
- Schedule a 15-minute retro to discuss the AI completion patterns with your pair programming partner.

*Generated by vibe-log-cli v1.2.3 | Session ID: clc_20240517_1422*