gabriel / muse public
blame.md markdown
90 lines 2.7 KB
Raw
sha256:f6cd81bc71702f5c1c6890bd39aaba994fe58c75f019d7c03934724fa2739bb4 fix: carry dev changes harmony dropped in merge — detached … Sonnet 4.6 minor ⚠ breaking 43 days ago

muse blame — line-level attribution for text files

muse blame shows which commit last modified each line of a text file tracked in state/. It is the universal, domain-agnostic attribution tool — the core VCS equivalent of git blame.

For domain-specific attribution, see:

  • muse midi note-blame — per-bar attribution in MIDI tracks
  • muse code blame — per-symbol attribution in code files

Usage

muse blame README.md
muse blame --ref v1.0.0 docs/design.md
muse blame --porcelain state/config.toml | jq '.commit_id'
muse blame --short 8 src/main.py

Options

Flag Default Description
--ref, -r HEAD Commit or branch to blame from
--porcelain, -p false Emit JSON objects instead of human-readable output
--short 12 Length of commit SHA prefix to display

Output (human-readable)

cccccccc0000  (Test User       2026-03-19)   1  hello world

Columns:

  • Commit SHA prefix (12 chars by default)
  • Author name (padded)
  • Date (YYYY-MM-DD)
  • Line number (right-aligned)
  • Line content

Output (--porcelain)

One JSON object per line:

{"lineno": 1, "commit_id": "cccccccc…", "author": "Test User", "committed_at": "2026-03-19T14:22:01+00:00", "message": "initial commit", "content": "hello world"}

How attribution works

The blame algorithm walks the commit graph backwards from the requested ref:

  1. Every line in the file at HEAD is initially attributed to HEAD.
  2. For each ancestor commit, a unified diff is computed between the ancestor's version and its child's.
  3. Lines that appear unchanged in both versions are re-attributed to the ancestor — the older commit that first introduced them.
  4. Lines that were added by a commit remain attributed to that commit.

This is equivalent to Git's blame algorithm for linear histories. For merge commits, the algorithm chooses the first parent to keep attribution clean.

Agent workflows

Find who introduced a bug

muse blame --porcelain src/parser.py \
  | jq 'select(.content | test("legacy_mode")) | .commit_id' \
  | sort -u

Audit a configuration file

muse blame config/production.toml

Annotate every line with its commit

muse blame --porcelain README.md > blame-report.jsonl

Limitations

  • Only text files are supported. Binary files (images, MIDI, etc.) should use domain-specific blame commands.
  • The walk follows the first-parent chain for merge commits. To attribute across both parents, use muse midi note-blame or muse code blame which are domain-aware.

Exit codes

Code Meaning
0 Success
1 File not found at the specified ref, or ref not found
File History 3 commits
sha256:d8316ffae901be06347e16ab55be11868eb519dd16ade3e8aa16a99e662f7e62 baseline: rc14 re-baseline after rc3 store corruption recovery Human patch 26 days ago
sha256:fb67fed5a4d3e40de84bdd163de94ef1386570bef1dd1a020a732c8a038962ce Merge branch 'dev' into main Human 48 days ago
sha256:1c4b3e3a9a1f300774c3ee662b572a698d5fd405bf765a71e6011a2e9c3eaaaa feat: Muse — version control for the agent era Human 100 days ago