/check-licenses
Check all dependency licenses for compliance with project requirements.
$ npx -y skills add rohitg00/awesome-claude-code-toolkit --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/check-licenses
Context preview
What this command does when you run it.
Check all dependency licenses for compliance with project requirements.
Command definition
check-licenses.mdname: check-licenses
description: Check all dependency licenses for compliance with project requirements.
/check-licenses - Check License Compliance
Check all dependency licenses for compliance with project requirements.
Steps
1. Detect the package manager: npm, pip, Maven, Gradle, Cargo, Go modules 2. List all direct and transitive dependencies with their versions 3. Retrieve the license type for each dependency 4. Classify licenses: permissive (MIT, Apache-2.0, BSD), copyleft (GPL, AGPL), other 5. Check dependencies against the project's allowed license list 6. Flag any copyleft licenses that may require source code disclosure 7. Identify dependencies with unknown, missing, or custom licenses 8. Check for license compatibility with the project's own license 9. Detect dual-licensed packages and determine which license applies 10. Generate a compliance report: dependency, version, license, status (allowed/flagged/unknown) 11. Calculate the total count by license type 12. Flag any newly added dependencies since the last check
Rules
- Default allowed licenses: MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, 0BSD
- Always flag AGPL and GPL licenses as they require careful review
- Check transitive dependencies, not just direct dependencies
- Verify license files exist in dependency packages, not just package.json declarations
- Handle SPDX license expressions (AND, OR, WITH exceptions)
- Report on development-only dependencies separately (less restrictive)
- Update the allowed license list through project configuration, not hardcoding
Read more
name: check-licenses description: Check all dependency licenses for compliance with project requirements.
/check-licenses - Check License Compliance
Check all dependency licenses for compliance with project requirements.
Steps
1. Detect the package manager: npm, pip, Maven, Gradle, Cargo, Go modules 2. List all direct and transitive dependencies with their versions 3. Retrieve the license type for each dependency 4. Classify licenses: permissive (MIT, Apache-2.0, BSD), copyleft (GPL, AGPL), other 5. Check dependencies against the project's allowed license list 6. Flag any copyleft licenses that may require source code disclosure 7. Identify dependencies with unknown, missing, or custom licenses 8. Check for license compatibility with the project's own license 9. Detect dual-licensed packages and determine which license applies 10. Generate a compliance report: dependency, version, license, status (allowed/flagged/unknown) 11. Calculate the total count by license type 12. Flag any newly added dependencies since the last check
Rules
- Default allowed licenses: MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, 0BSD
- Always flag AGPL and GPL licenses as they require careful review
- Check transitive dependencies, not just direct dependencies
- Verify license files exist in dependency packages, not just package.json declarations
- Handle SPDX license expressions (AND, OR, WITH exceptions)
- Report on development-only dependencies separately (less restrictive)
- Update the allowed license list through project configuration, not hardcoding
The most comprehensive toolkit for Claude Code -- 135 agents, 35 curated skills (+400,000 via SkillKit), 42 commands, 176+ plugins, 20 hooks, 15 rules, 7 templates, 15 MCP configs, 26 companion apps, 53 ecosystem entries, and more.
Repo: rohitg00/awesome-claude-code-toolkit
Other commands on rohitg00-claude-code-toolkit.
- /adr
Write an Architecture Decision Record documenting a significant technical decision.
Open command - /design-review
Conduct a structured design review of a module, feature, or system component.
Open command - /diagram
Generate Mermaid diagrams from codebase analysis or description.
Open command - /migrate
Plan and execute a framework or library migration incrementally.
Open command - /plan
Create a structured implementation plan for the requested feature or change.
Open command - /refactor
Perform a systematic refactoring of the specified code area.
Open command

