devlog-harvester

Automates harvesting of development session data from git repositories.

1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/chipoto69/claude-skills --skill devlog-harvester
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devlog-harvester
Source: https://github.com/chipoto69/claude-skills/tree/main/devlog-harvester
Command: npx skills add https://github.com/chipoto69/claude-skills --skill devlog-harvester

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, tokei, cloc, and includes scripts (resource) components.

What problem does it solve?

This skill automates the collection of development session data, git activity, and project context, reducing manual tracking and report generation.

Core Features & Use Cases

  • Session harvesting: capture per-project activity, timelines, and touched files for audits and knowledge management.
  • Git activity aggregation: summarize commits, diffs, and author activity for sprint reviews.
  • Context enrichment: detect project tech stack and LOC statistics to inform documentation.

Quick Start

Run /harvest to capture the current development session for the active project.

Frequently Asked Questions about devlog-harvester

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

FAQPage Schema
How do I automatically capture development session data and git activity?

You can automate development session capture by running a harvest command that aggregates git commits, diffs, and touched files into structured session data. This eliminates manual tracking for audits and sprint reviews.

What is the best way to generate LOC statistics and tech stack context for project documentation?

Generating LOC statistics and tech stack context is best handled by static project analysis tools like tokei or cloc. They detect project metrics automatically to inform documentation and knowledge stores.

Do I need git and tokei installed to harvest project context and commits?

Yes, you need git, tokei, and cloc installed locally. The session harvesting process leverages these dependencies to aggregate commit data and compute lines of code statistics for project context enrichment.

Can I aggregate git commit history and author activity for sprint reviews automatically?

Yes, you can aggregate git commit history and author activity automatically. The harvester operates across git commits and project switches to summarize diffs and author activity for sprint reviews.

How do I export development session data to an Obsidian knowledge store?

Exporting development session data to an Obsidian knowledge store involves gathering structured session context from your repository. The harvester produces this structured data for knowledge-forge integration.

What are the limitations of automating dev session capture across project switches?

Automating dev session capture across project switches relies on local tooling and static analysis. It may not capture external context or non-git activities, focusing strictly on repository commits and local file metrics.