dev.add-license

Add an Apache-2.0 license to a repository using git config.

6|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/kevinslin/llm --skill dev-add-license
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev.add-license
Source: https://github.com/kevinslin/llm/tree/main/skills/dev.add-license
Command: npx skills add https://github.com/kevinslin/llm --skill dev-add-license

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill automates adding a compliant open source license to a repository by generating a LICENSE file using the Apache-2.0 template and ensuring the license information is wired into package.json when applicable.

Core Features & Use Cases

  • Automates license creation by copying the Apache-2.0 template into the target repo.
  • Detects copyright owner from git config and appends the proper year.
  • Updates package.json license field when present to Apache-2.0.

Quick Start

Run the add-license workflow to create an Apache-2.0 LICENSE and update package.json if present.

Frequently Asked Questions about dev.add-license

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

FAQPage Schema
How do I add an Apache-2.0 license to my repository automatically?

To add an Apache-2.0 license automatically, this skill copies the LICENSE-APACHE-2.0 template to your project root, appends the copyright notice using your git config user.name and the current year, and updates the license field in package.json if present.

What is the best way to update package.json with the correct open-source license?

Updating package.json with the correct open-source license is handled automatically by detecting the file in the project root and setting its license field to Apache-2.0 during the license file generation process.

Do I need git config to generate a license file with a copyright notice?

Yes, you need git config user.name to generate a license file with a copyright notice. The skill extracts the copyright owner directly from this git configuration to append the proper attribution to the Apache-2.0 template.

How does repository automation handle missing package.json when adding a license?

Repository automation handles missing package.json by focusing on creating the LICENSE file from the Apache-2.0 template. It updates package.json only when the file is already present in the identified project root.

Why does my Apache-2.0 license template need the current year appended?

The Apache-2.0 license template needs the current year appended to form a valid copyright notice. The automation retrieves the current year dynamically and combines it with the copyright owner from git config to complete the legal requirement.