copyright-headers

Automate Apache-2.0 copyright header insertion and updates across Go, YAML/TOML, shell scripts, and Makefiles.

10|14|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/openkaiden/kdn --skill copyright-headers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copyright-headers
Source: https://github.com/openkaiden/kdn/tree/main/.agents/skills/copyright-headers
Command: npx skills add https://github.com/openkaiden/kdn --skill copyright-headers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the addition and maintenance of Apache-2.0 copyright headers across common file types in a codebase.

Core Features & Use Cases

  • Add headers to Go, YAML/TOML, shell scripts, and Makefiles.
  • Update existing headers to reflect the current year and range rules.
  • Respect special cases like shebangs and YAML directives; generate a change report.

Quick Start

Run the tool in a project directory to scan for eligible files and apply headers according to policy.

Frequently Asked Questions about copyright-headers

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

FAQPage Schema
How do I automatically add Apache 2.0 copyright headers to Go, YAML, and shell scripts?

To automatically add Apache 2.0 copyright headers to Go, YAML, and shell scripts, run a scanning tool in your project directory to detect eligible files and apply formatted headers according to your policy.

What is the best way to update existing copyright headers with the current year across a codebase?

Updating existing copyright headers with the current year involves scanning your codebase to detect outdated headers and applying range rules to insert or update the year formatting automatically across supported file types.

Does adding copyright headers to shell scripts and Makefiles respect shebangs and YAML directives?

Yes, adding copyright headers to shell scripts and Makefiles respects special cases like shebangs and YAML directives by ensuring the header is inserted correctly after these initial file lines without breaking execution.

How do I generate a report detailing new, updated, and skipped files when applying license headers?

Generating a report detailing new, updated, and skipped files when applying license headers is handled automatically by the tool after it scans and processes your codebase, providing a summary of all changes made.

Can I use an automated tool to maintain Apache 2.0 headers across diverse repositories with different file types?

Yes, you can use an automated tool to maintain Apache 2.0 headers across diverse repositories with different file types, handling common formats like Go, YAML, TOML, shell scripts, and Makefiles consistently.