Trace git line history to commits, pull requests, and requirement GUIDs.
npx skills add https://github.com/alexmensch/claude-sdlc-plugins --skill blame
Please help me install this Agent Skill. Skill: blame Source: https://github.com/alexmensch/claude-sdlc-plugins/tree/main/plugins/debugging/skills/blame Command: npx skills add https://github.com/alexmensch/claude-sdlc-plugins --skill blame
This Skill helps developers and maintainers trace lines of code back through git history to the original requirements that motivated the changes, reducing time spent investigating why code exists and enabling accountability.
Trace the origin of src/app/main.py lines 40–70 back through git and GitHub to its requirements GUID and spec file.
High-intent search queries and answers about installing and using this skill.
To trace git blame back to product requirements, this Skill maps file lines through git history to originating commits, resolves them to pull requests via the GitHub API, and extracts referenced requirement GUIDs to locate matching spec files for audit or compliance workflows.
Code archaeology for tracing pull requests to spec files involves analyzing a file's full line history to identify originating commits, resolving those commits to pull requests, and extracting requirement GUIDs from PR bodies to map code changes directly to product spec files.
Yes, you need GitHub API access or a GitHub remote to map git commits to requirement GUIDs, because the Skill resolves local git history commits to pull requests and extracts the referenced requirement GUIDs directly from the PR body text.
To prepare a product directory for requirement traceability analysis, populate it with spec files containing unique GUIDs so the Skill can match extracted pull request references against them and return the exact requirement content motivating the code change.
Yes, you can use git blame for incident forensics and compliance auditing, as the Skill traces specific file lines through git history to identify originating commits, pull requests, and matched requirement spec files to establish historical design accountability.
Without spec file GUIDs in the product directory, tracing code history is limited to identifying commit authors, messages, and timestamps, because the Skill cannot resolve pull request references to matching requirement content without unique GUID identifiers.
twikusSynchronize local ~/.claude configuration folders to the repository with rsync --delete.
docs-plusReview code changes between a fixed point and HEAD for standards and spec compliance.
alexmenschConvert pull request IDs or requirements files into dated Markdown changelog entries.
rtfpessoaAnalyze file dependencies to organize staged changes into atomic Git commits.
