dev.add-license_skill

This skill adds an Apache-2.0 LICENSE file to a repository, auto-filling copyright from git and updating package.json when present.

JavaScript

5

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill kevinslin/llm --skill dev.add-license

SKILL.md3.2 KB

Overview

This skill adds an Apache License 2.0 file to a repository and automatically populates copyright information from git configuration. It can place the LICENSE in the chosen project directory and will update package.json's license field to "Apache-2.0" if present. It confirms the actions taken and the copyright details used.

How this skill works

The skill determines the target directory (current folder or repository root) and tries to read the local git user.name for the copyright owner. It copies a standard Apache 2.0 template into a LICENSE file, appends a populated copyright notice with the current year and owner, and checks for package.json. If package.json exists, it updates or inserts the "license" field to "Apache-2.0" and writes the file back while preserving formatting.

When to use it

You want to add an Apache 2.0 LICENSE file to a project quickly.
You want the copyright owner auto-filled from git configuration.
You need package.json updated to reflect the repository license.
You are in a subdirectory and want the LICENSE at repo root or current dir.
You prefer a standard, reproducible license addition workflow.

Best practices

Run the skill from the intended target directory or confirm whether to use repository root.
Ensure git user.name is set if you want automatic copyright detection.
Review the generated LICENSE file and appended copyright notice before committing.
Back up package.json or use version control so you can review the license field change.
If git config is not set or you prefer a different owner name, provide it explicitly when prompted.

Example use cases

A maintainer wants to add Apache 2.0 license to a new project and set package.json license correctly.
A contributor needs a properly formatted LICENSE at the repository root while working from a subfolder.
An automation step in a repository bootstrap that ensures a license file and package.json license are present.
A user without a configured git name provides the copyright owner interactively and gets a completed LICENSE file.

FAQ

It first attempts to read git config user.name. If that is unavailable or incorrect, you can provide the copyright owner name manually.

Will the skill overwrite an existing LICENSE or package.json?

The skill will create or overwrite LICENSE in the target directory and will update or replace the license field in package.json; review changes before committing.