attribution-advisory

Scan unified diffs for authorship, copyright, and licensing changes.

Updated May 2, 2026
One-click install
npx skills add https://github.com/denson/the-stoa --skill attribution-advisory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: attribution-advisory
Source: https://github.com/denson/the-stoa/tree/main/substrate/skills/attribution-advisory
Command: npx skills add https://github.com/denson/the-stoa --skill attribution-advisory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill reports attribution changes in unified diffs, flagging modified or deleted lines without blocking or denying commits, thus preserving workflow continuity.

Core Features & Use Cases

  • Attribution Change Detection: Detects modifications or deletions of author, copyright, or license lines.
  • Secondary Check: Flags new non-principal author-like fields in non-vendored paths.
  • Safe Reporting: Never blocks or fails a commit, always exits zero status.
  • Use Case: Before committing or merging, run the skill to check for attribution issues and ensure proper authorship.

Quick Start

Run the attribution-advisory skill on your diff or staged changes using the command 'run attribution-advisory'.

Frequently Asked Questions about attribution-advisory

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

FAQPage Schema
How do I check for authorship and license changes in a diff without blocking commits?

You can scan unified diffs for modified or deleted authorship, copyright, and license lines using a pre-commit advisory check. This reports attribution changes while always exiting with a zero status to avoid halting your workflow.

What is a non-blocking pre-commit hook for license compliance scanning?

A non-blocking pre-commit hook for license compliance scans staged changes for attribution modifications and reports them without denying the commit. It flags altered copyright or author lines but preserves workflow continuity by never failing the operation.

How do I detect new non-principal author-like fields in non-vendored code paths?

You can run a secondary check on your unified diff to flag newly added non-principal author-like fields in non-vendored paths. This detects unexpected authorship additions alongside standard copyright and license line modifications.

Do I need Python3 to run a diff analysis for commit safety checks?

Yes, you need Python3 installed to perform the scanning operations for attribution changes in unified diffs. The execution requires bash to run the script and Python3 to process the diff analysis.

How do I scan unified diffs for deleted copyright and author lines before merging?

You can execute a scan on your staged changes or diffs to detect deleted or modified copyright and author lines. The scan operates as an advisory report to ensure proper attribution is maintained before merging.

Will an attribution advisory check stop my git commit if it finds a licensing issue?

No, an attribution advisory check will never stop your git commit. It operates with safe reporting by always exiting with a zero status, ensuring proper attribution reporting without blocking or halting the development workflow.