SkillAgentSearch skills...

file-headers

MANDATORY for every coding agent (Claude Code, Codex, or any other) on every change-set — every applicable source file the agent creates or updates MUST start with the project's copyright/authorship header (file overview + exact author line).

Install / Use

npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill file-headers

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Automation

Supported Platforms

Claude Code
OpenAI Codex

Our assessment of file-headers

file-headers scores 86/100 on our quality scale, 1796th of 2,758 Automation skills we index.

Its SKILL.md is 4.1 KB long, split into 7 sections with 8 code examples: a solid amount of guidance for an agent.

With 1,015 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so file-headers is actively maintained.
  • Our last check on 2026-11-03 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

file-headers compared with similar skills

All 4 of these similar skills score higher than file-headers; compare them before choosing.

SkillScoreStarsUpdatedFormat
file-headers (this skill)by hoangsonww861.0k2mo agoSKILL.md
Agent-Reachby Panniantong100114.0ktodayCLAUDE.md
rufloby ruvnet10082.3ktodayCLAUDE.md
headroomby headroomlabs-ai10080.5ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10040.6k12d agoCLAUDE.md

Frequently asked questions

How do I install file-headers?
Run npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill file-headers. The install tabs above show the steps for each supported agent.
Which AI agents does file-headers work with?
It is written for Claude Code and OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
Is file-headers safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is file-headers still maintained?
The repository was last updated about 2 months ago, so file-headers is actively maintained.

name: file-headers description: MANDATORY for every coding agent (Claude Code, Codex, or any other) on every change-set — every applicable source file the agent creates or updates MUST start with the project's copyright/authorship header (file overview + exact author line). Use automatically whenever writing a new file or editing an existing one; do not wait to be asked. Covers JS/TS/TSX/CJS/MJS, Python, shell, and CSS. Includes the audit script to verify repo-wide compliance.

File Headers — Copyright Comment + File Overview

Every applicable source file in this repository starts with a header comment containing a file overview and the exact author line:

@author Son Nguyen <hoangson091104@gmail.com>

The name and email must be exactly as above — no variations, no substitutions, no other names. This applies to every coding agent working in this repo (Claude Code, Codex, or any other tool): when you create a new applicable file, write the header first; when you update an existing applicable file that is missing the header, add it as part of the same change.

Applicable files

| Included | Excluded | | -------- | -------- | | *.js, *.ts, *.tsx, *.cjs, *.mjs | anything under node_modules/, dist/, build/, data/, .worktrees/ | | *.py, *.sh | vendored/minified files (*.min.js, wiki/mermaid.min.js) | | *.css | generated files (wiki/i18n-content.js — carries its own AUTO-GENERATED banner) | | | snapshots (__snapshots__/), lockfiles, JSON/YAML/Markdown |

Header formats by file type

JS / TS / TSX — server & scripts style (overview inline in @file):

/**
 * @file One-to-few-sentence overview of what this file does and why it
 * exists. Mention the key contracts or invariants the file owns.
 * @author Son Nguyen <hoangson091104@gmail.com>
 */

JS / TS / TSX — client style (@file name + @description overview), used under client/src/:

/**
 * @file ComponentName.tsx
 * @description What the component/module renders or provides and how it fits
 * into the app.
 * @author Son Nguyen <hoangson091104@gmail.com>
 */

CSS (same block-comment shape as client/src/index.css):

/**
 * @file file.css
 * @description What these styles cover.
 * @author Son Nguyen <hoangson091104@gmail.com>
 */

Shell (# block right after the shebang; existing overview comments count — just make sure the @author line is in the block):

#!/usr/bin/env bash
# script-name.sh — what the script does, one to few lines.
# @author Son Nguyen <hoangson091104@gmail.com>

Python (inside the module docstring):

"""
module.py — what the module does.

@author Son Nguyen <hoangson091104@gmail.com>
"""

Rules

  1. New file → header first. Any applicable file you create starts with the header before any code (after the shebang for scripts).
  2. Touched file missing header → add it. If you edit a file that lacks the header, add one in the same commit. Write a real overview — describe what the file actually does; never a placeholder like "TODO" or "utility file".
  3. Exact author line. @author Son Nguyen <hoangson091104@gmail.com> — byte-exact, in every file type (shell and Python use it inside # / docstring comments).
  4. Don't churn existing headers. If a file already has a compliant header, leave it alone unless the file's purpose changed (then update the overview).
  5. Overviews must stay truthful. When an edit changes what a file does, update its @file/@description overview in the same change.

Audit

Run the bundled checker to list any applicable file missing the header:

bash .claude/skills/file-headers/scripts/check-headers.sh

Exit code 0 = fully compliant; 1 = the printed files are missing headers. Run it before finishing any change-set that adds files, and during reviews.

On every pull request, GitHub Actions runs .claude/skills/file-headers/scripts/check-headers-pr.sh against only the files changed in the PR diff (added, copied, renamed, or modified). Test locally before pushing:

bash .claude/skills/file-headers/scripts/check-headers-pr.sh origin/master HEAD

Related Skills

View on GitHub
GitHub Stars1.0k
CategoryAutomation
Updated2mo ago
Forks238

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions