wip-license-guard

Automate license compliance checks and enforcement across code repositories.

3|Updated Feb 28, 2026

Search Tags:#compliance #license #copyright #repo #mit #agpl #cla

Ready to run

npx skills add https://github.com/wipcomputer/wip-ai-devops-toolbox --skill wip-license-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wip-license-guard
Source: https://github.com/wipcomputer/wip-ai-devops-toolbox/tree/main/tools/wip-license-guard
Command: npx skills add https://github.com/wipcomputer/wip-ai-devops-toolbox --skill wip-license-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that all your code repositories adhere to consistent licensing and copyright standards, preventing compliance issues and protecting your intellectual property.

Core Features & Use Cases

License Enforcement: Automatically checks for and enforces correct LICENSE files, copyright headers, and dual-license (MIT/AGPL) compliance.
CLA Management: Ensures a Contributor License Agreement (CLA.md) is present.
README Standardization: Standardizes the license section in your main README files and removes them from sub-tool READMEs.
Use Case: Before merging a pull request, this Skill can automatically verify that all new and modified files have the correct copyright notice and that the main LICENSE file is up-to-date, preventing accidental non-compliance.

Quick Start

Run wip-license-guard check in your repository to audit its license compliance.

Frequently Asked Questions about wip-license-guard

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

FAQPage Schema

How do I automate license compliance checks and enforce copyright headers across a code repository?▼

To automate license compliance checks, you can run a repository audit command that validates LICENSE files, copyright headers, CLA presence, and README license sections. This enforces consistent copyright standards across your code repositories before merging pull requests.

What does dual-license MIT and AGPL enforcement involve for an open source repo?▼

Dual-license MIT and AGPL enforcement validates that your repository correctly adheres to both licensing models. The compliance check ensures the appropriate LICENSE files and copyright notices are present and properly maintained across the codebase.

How do I check if a Contributor License Agreement (CLA.md) is present before merging a pull request?▼

To check if a Contributor License Agreement is present, run an automated compliance audit on your repository. This verifies that a CLA.md file exists and validates copyright headers alongside other licensing requirements before pull request integration.

Can I automatically fix missing copyright notices and standardize README license sections?▼

Yes, you can automatically fix missing copyright notices and standardize README license sections. The interactive setup and auto-fixing capabilities correct identified issues, including removing license sections from sub-tool READMEs.

Do I need any external dependencies to validate repository licensing and copyright compliance?▼

No external dependencies are required to validate repository licensing and copyright compliance. The tool operates independently to check LICENSE files, CLA presence, and dual-license adherence directly within your codebase.