git-timesheet

Convert git commit history into Solidtime time entries.

2|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/biztechprogramming/bond --skill git-timesheet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-timesheet
Source: https://github.com/biztechprogramming/bond/tree/main/skills/git-timesheet
Command: npx skills add https://github.com/biztechprogramming/bond --skill git-timesheet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform git commit history into Solidtime time entries to track work done in codebases, reducing manual entry and improving traceability.

Core Features & Use Cases

  • Extracts commit history from local repos to generate time-entry proposals.
  • Groups commits into logical work chunks with dates, descriptions, and relative sizes.
  • Maps work chunks to Solidtime projects via MCP integration and prompts user for ambiguous mappings.
  • Presents a reviewable table of proposed entries for confirmation before creation.

Quick Start

Point the AI to a local git repository and a date window, and it will generate proposed Solidtime entries from the commit history for review.

Frequently Asked Questions about git-timesheet

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

FAQPage Schema
How do I convert git commit history into billable time entries?

You can convert git commit history into billable time entries by parsing local repository commits, authors, dates, and diff stats to generate structured work chunks for review and import into time tracking platforms.

Can I automatically track time in Solidtime from my local git repositories?

Yes, you can automatically track time in Solidtime from local git repositories by mapping grouped commit history to Solidtime projects via MCP integration, prompting for ambiguous mappings, and presenting entries for confirmation before creation.

Does generating a timesheet from git logs require manual project mapping?

Generating a timesheet from git logs does not require fully manual project mapping. The Skill automatically maps work chunks to Solidtime projects via MCP integration and only prompts the user for confirmation when encountering ambiguous mappings.

What do I need to connect git history to Solidtime time tracking?

To connect git history to Solidtime time tracking, you need access to local git repositories, integration with Solidtime MCP, and a specified date window to extract and group commits into logical work chunks for review.

How are multiple commits grouped together when creating time entries from git history?

When creating time entries from git history, multiple commits are grouped into logical work chunks that include dates, descriptions, and relative sizes, which are then presented as a reviewable table for confirmation before final creation.