data-license

Review code changes against the Helm Log data licensing policy.

2|2|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/weaties/helmlog --skill data-license
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-license
Source: https://github.com/weaties/helmlog/tree/main/.claude/skills/data-license
Command: npx skills add https://github.com/weaties/helmlog --skill data-license

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps ensure that code changes comply with the Helm Log data licensing policy, preventing potential legal and ethical issues related to data handling and sharing.

Core Features & Use Cases

  • Policy Review: Compares code changes against specific sections of the data licensing policy.
  • Compliance Checklist: Provides a structured checklist for reviewing data-touching code.
  • Use Case: Before merging a new feature that modifies how user data is stored or shared, run this Skill to verify it adheres to all data ownership, sharing, and retention rules.

Quick Start

Review the current code changes against the data licensing policy.

Frequently Asked Questions about data-license

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

FAQPage Schema
How do I check if my code changes comply with data licensing policies?

To check code compliance with data licensing policies, review data-touching code against specific policy sections for ownership, sharing, retention, AI/ML, commercial use, and liability. This verifies technical requirements like audit logging and rate limiting are met.

What does a data policy compliance review cover for code handling user data?

A data policy compliance review covers code changes touching user data by checking them against sections for ownership, sharing, retention, AI/ML, commercial use, and liability, ensuring technical requirements like audit logging and rate limiting are met.

How do I verify data retention and sharing rules before merging a new feature?

To verify data retention and sharing rules before merging, run a policy review against code changes. It provides a structured checklist for reviewing data-touching code to ensure it adheres to all data ownership, sharing, and retention rules.

Does the compliance review check for technical requirements like audit logging?

Yes, the compliance review checks for technical requirements like audit logging and rate limiting. It identifies data-touching code and ensures these technical controls are met alongside policy sections for ownership and liability.

Can I use this for reviewing AI and ML data usage in my code?

Yes, you can use this for reviewing AI and ML data usage. It compares code changes against the data licensing policy sections specifically covering AI/ML, alongside commercial use, ownership, sharing, and retention rules.

When do I need to run a data license compliance check on my code?

You need to run a data license compliance check before merging a new feature that modifies how user data is stored or shared. It prevents potential legal and ethical issues related to data handling and sharing.