Local Git analytics: inspect the evidence behind a change
Start with the repository, not a score
Git history records commits, authorship metadata, timestamps, and changes. That record is useful for finding a change and recovering its context. It does not measure time spent, personal productivity, or business value.
GitGlow connects this inspection to a local Git and coding-agent workflow: choose a trusted repository, inspect the current state, follow relevant history, and decide what needs attention.
A practical first review
- Open and explicitly trust a local repository.
- Inspect staged, unstaged, and untracked changes before starting new work.
- Review the branches and commits relevant to your question.
- Read the actual diff before making a claim about what changed.
- Bring in authorized GitHub reviews and checks when available in your plan.
A dated history view and a dirty working tree answer different questions. Commit timestamps locate recorded commits in a period. The dirty working tree is current state; it is not evidence of when an edit happened.
Local history and GitHub samples have different scope
Local inspection can include unpushed commits and branches in your clone. An authorized GitHub view adds remote repository context without requiring a clone for every review. Remote Insights uses a bounded sample of up to 100 default-branch commits and labels it accordingly. Neither source should be described as a complete record of every activity around a project.
When coding agents are involved
Agent Observatory adds supported provider events and independent working-tree observations. Observed Codex or Claude sessions remain owned by their originating client. GitGlow-managed Pro runs can expose supported controls. Replay is a sanitized, bounded local record, not a full transcript or hidden reasoning.
Follow the agent-work walkthrough for a concrete sequence from observation through review and an editable Indie Log.Review before a release
Use the relevant diff, available checks, and changes since the last tag to prepare a release discussion. Pro Release Workspace helps prepare release material and requires a separate confirmed publication action. An agent completion or a burst of commits is not release evidence.
Choose the right starting point
Free includes local inspection, one trusted-repository observation, one live observed agent or MCP run, basic Activity Tape, manual Indie Log, and the latest completed Replay for 24 hours. Pro adds concurrent repositories and agents, managed runs, authorized GitHub context, Release Workspace, and managed Indie Log report packs. Provider usage remains the user’s responsibility.
See current plans or download GitGlow.Keep data boundaries visible
Local repository inspection stays on the device. GitHub authorization, billing, and optional managed analysis involve their respective services. Managed Indie Log analysis begins with a selected repository/date scope and a disclosure preview. Read that disclosure before generation and review the evidence before publishing a claim.
Read the privacy policy.