liveBook · Manning

Granularity

As explained in Crack Any Codebase with AI

Granularity is the level of detail at which an item or collection of items is examined.

Granularity sets how much detail each selected item receives. In Git history, filtering chooses which commits appear; granularity chooses whether each commit is shown as metadata, touched files, or code changes. section 6.2

Choosing a useful zoom

To find abandoned features, combine file-level detail with `git log --diff-filter=D --name-only`. To understand one implementation, use `git show <hash>`; staying at commit level would hide the relevant files and lines. section 6.2

How Crack Any Codebase with AI covers it

How deep it goes
Defines three additive Git levels and contrasts their outputs, without developing broader analytical interpretation.
Examples
Uses Git log commands, deleted-file listings, a full commit, and a members-auth middleware change.
What it assumes
Assumes familiarity with Git history and commits while defining the distinction between filters and detail levels.
What you can do after
Apply it via Git commands to choose an effective zoom level for repository questions.
How it connects
Connects Git history with filters, commits, files, code changes, and repository analysis.

Also explained in

Compare how 13 books explain granularity →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Crack Any Codebase with AI. The section links point to the parts of the book it draws on.