skills.rest
sanskarbasnet
sanskarbasnetCOMMUNITY
Explore all skills by this author →
GitHub

blame

Merge git blame data with brain intents and decisions for a file or line.

1|Updated May 4, 2026
Search Tags:#git#decisions#intent#brain#blame#code-history
One-click install
npx skills add https://github.com/sanskarbasnet/fstack --skill blame-sanskarbasnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blame
Source: https://github.com/sanskarbasnet/fstack/tree/main/blame
Command: npx skills add https://github.com/sanskarbasnet/fstack --skill blame-sanskarbasnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brain-aware blame on a file or file:line. Combines git blame (who/when/commit) with the brain (which intent introduced this work, decisions affecting the file, recent edits log). Answers "why is this here?" in one shot. (fstack)

Core Features & Use Cases

  • Integrates line-level git blame with brain context to surface intent and decisions behind changes.
  • Lets you trace the evolution of a file by tying commits to brain edits and decisions.
  • Use Case: When investigating a suspicious change, run blame to see who touched the line and why it was introduced.

Quick Start

Type the blame command with a file path (and optional line) to retrieve a combined git brain-blame.

Frequently Asked Questions about blame

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

FAQPage Schema
How do I find out why a specific line of code was changed using git blame?▼

Git blame shows who changed a line and when, but combining it with a brain context log surfaces the intent and decisions behind the commit to explain why the code exists.

What is the best way to trace the intent behind a code change during an audit?▼

Tracing intent during a code audit requires merging git blame data with a decisions store, linking the commit history directly to the reasoning and recent edits that introduced the change.

Can I retrieve git blame and related decisions for a specific file path?▼

Yes, you can query a specified file or file line to retrieve a unified view containing commit info, line content, related intents, and recent brain edits affecting that file.

Does this brain-aware blame approach work for standard debugging workflows?▼

Yes, this approach applies directly to code investigations and debugging workflows by surfacing the commit info and historical decisions behind suspicious changes in a single query.

What do I need to integrate git blame with brain context for code history analysis?▼

Integrating git blame with brain context requires access to the brain's edits log and decisions store to produce a unified view of code history, intents, and commit data.

Related Skills

Explore More Software Engineering Skills→
mistakenotmistakenot

contextual-commit

Write Conventional Commit messages with typed scoped action lines for git commits.

Community
Intermediate
fabriqaaifabriqaai
201

walkthrough-generate

Generate a template-driven implementation walkthrough from run logs and intents.

Official
Intermediate
sanskarbasnetsanskarbasnet
1

why

Surface decisions, intents, and recent edits for a file or symbol.

Community
Intermediate
berkcangumusisikberkcangumusisik
11

git-blame-explain

Explain code line origins using git blame and commit history.

Community
Intermediate