notify-blame

Identify Git blame authors and notify them on Slack with MR links.

4|Updated Apr 10, 2023
One-click install
npx skills add https://github.com/dudeofawesome/nix-config --skill notify-blame
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notify-blame
Source: https://github.com/dudeofawesome/nix-config/tree/main/modules/presets/home-manager/paciolan/llms/skills/notify-blame
Command: npx skills add https://github.com/dudeofawesome/nix-config --skill notify-blame

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Notifying blame authors on Slack helps teams review changes quickly by providing context and accountability.

Core Features & Use Cases

  • DMs blame authors with the MR link and a per-author summary, enabling faster reviews.
  • Auto-detects the MR URL from the current branch, explicit argument, or prior chat context; resolves the repo and MR number for precise targeting.
  • Maps each blame author to a Slack user via the person-to-user-map workflow and delivers personalized summaries.

Quick Start

Use the slash command /notify-blame to automatically DM affected authors; provide an MR URL to override automatic detection if needed.

Frequently Asked Questions about notify-blame

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

FAQPage Schema
How do I notify Git blame authors on Slack about a new merge request?

To notify Git blame authors on Slack, use the /notify-blame command. It identifies code authors from Git diffs, maps them to Slack users, and sends direct messages containing the MR link and a summary of their specific code changes.

Can I automatically detect the GitLab merge request URL from my local branch?

Yes, you can automatically detect the GitLab merge request URL. The tool resolves the MR URL directly from your current local branch context, or alternatively uses the GitLab CLI, explicit arguments, or prior chat history for precise targeting.

Do I need Python to run scripts that map Git authors to Slack users?

Yes, you need Python 3 to run the bundled git-blame-authors.py script. The script requires Python 3, the git CLI, and configured Slack integration access to successfully map Git authors to Slack users and deliver messages.

What is the best way to hold developers accountable for code changes during a review?

The best way to hold developers accountable for code changes during a review is DMing blame authors with MR context. It builds per-author summaries from diffs and sends personalized Slack messages, providing clear context and accelerating the review process.

How does mapping Git blame authors to Slack users work for code reviews?

Mapping Git blame authors to Slack users works by analyzing branch diffs to identify contributors, then using a person-to-user-map workflow. It builds per-author summaries from the code changes and delivers them as direct Slack messages with the MR link.

What are the limitations of auto-resolving a merge request URL from local context?

A limitation of auto-resolving a merge request URL from local context is potential detection failure if the branch lacks clear GitLab tracking. You can override automatic detection by explicitly providing an MR URL as an argument to ensure accurate Slack notifications.