hpe-copyright
Skill2 starsChanged 11 months agoMITView on GitHub
Check, add, or fix HPE copyright headers in source files. Use this skill when (1) Adding copyright headers to new files, (2) Checking if files have valid copyright headers, (3) Updating outdated copyright years, (4) Preparing code for CI that enforces copyright headers, (5) User mentions "copyright", "HPE header", or "copyright check". Format is "Copyright YYYY-YYYY Hewlett Packard Enterprise Development LP" as a comment on the first line.
In this repository5 other files it gives its agents.
- docs-fetcherSkill
- fastapi-code-reviewSkill
- jira-workflowSkill
- multi-agent-debate-reviewSkill
- skill-creatorSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ensure all source files have the required HPE copyright header to pass CI checks.
- Very specific: line 59
Missing header: Add Copyright CURRENT_YEAR-CURRENT_YEAR Hewlett Packard Enterprise Development LP
- Very specific: line 60
Outdated year: Update only the second year to current year (e.g., 2024-2024 → 2024-2025)
- Distinctive: line 65
When manually adding or fixing a copyright header:
- Distinctive: line 68
Add as the very first line of the file
- Very specific: line 69
Use current year for both years if creating new: Copyright 2025-2025 Hewlett Packard Enterprise Development LP
- Distinctive: line 70
If updating existing, only change the second year
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
HPE Copyright Header Management
Ensure all source files have the required HPE copyright header to pass CI checks.
Copyright Format
Copyright {start_year}-{end_year} Hewlett Packard Enterprise Development LP- start_year: Year the file was created
- end_year: Current year (must be updated annually)
- Placement: First line of the file, as a comment
Examples by Language
| Language | Copyright Line |
| Python | # Copyright 2024-2025 Hewlett Packard Enterprise Development LP |
| JavaScript/TypeScript | // Copyright 2024-2025 Hewlett Packard Enterprise Development LP |
| Go | // Copyright 2024-2025 Hewlett Packard Enterprise Development LP |
| SQL | -- Copyright 2024-2025 Hewlett Packard Enterprise Development LP |
| HTML/XML | <!-- Copyright 2024-2025 Hewlett Packard Enterprise Development LP --> |
| CSS | /* Copyright 2024-2025 Hewlett Packard Enterprise Development LP */ |
Quick Reference
Check all files (dry run)
python scripts/copyright_check.py /path/to/repo --dry-runFix all files
python scripts/copyright_check.py /path/to/repoCI check mode (fails if issues found)
python scripts/copyright_check.py /path/to/repo --check-onlyRules
- Missing header: Add
Copyright CURRENT_YEAR-CURRENT_YEAR Hewlett Packard Enterprise Development LP - Outdated year: Update only the second year to current year (e.g.,
2024-2024→2024-2025) - Exclusions: Respects both
.gitignoreand.copyrightignorefiles (gitignore-style patterns)
Manual Fixes
When manually adding or fixing a copyright header:
- Determine the correct comment syntax for the file type
- Add as the very first line of the file
- Use current year for both years if creating new:
Copyright 2025-2025 Hewlett Packard Enterprise Development LP - If updating existing, only change the second year
Supported File Types
The script supports 50+ file extensions including:
- Hash (#):
.py,.sh,.rb,.pl,.r,.jl - Double-slash (//):
.js,.ts,.jsx,.tsx,.go,.c,.cpp,.java,.kt,.swift,.rs - Dash-dash (--):
.sql,.lua,.hs - Block comments:
.html,.xml,.css,.vue
Exclusion Patterns
The script automatically reads patterns from both .gitignore and .copyrightignore in the repo root. Use .copyrightignore for additional exclusions specific to copyright checking:
# Directories
vendor/**
third_party/**
# File types not in .gitignore
*.generated.go
# Specific files
MakefileDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

