Skip to content

hoangsonww/Claude-Code-Agent-Monitor / .claude/skills/file-headers

file-headers

Verified

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.

FileKindSize
SKILL.mdskill md4.2 KB
scripts/check-headers-pr.shexecutablescript4.0 KB
scripts/check-headers.shexecutablescript1.2 KB

scripts/check-headers.sh

View on GitHub
#!/usr/bin/env bash
# check-headers.sh — audit the repo for applicable source files missing the
# mandatory copyright/authorship header (see .claude/skills/file-headers).
# Prints each non-compliant file; exits 0 when fully compliant, 1 otherwise.
# @author Son Nguyen <hoangson091104@gmail.com>

set -euo pipefail

ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/../../../.." && pwd)"
AUTHOR_MARK="@author Son Nguyen"

missing=0
while IFS= read -r f; do
  if ! grep -q "$AUTHOR_MARK" "$f"; then
    echo "MISSING HEADER: ${f#"$ROOT"/}"
    missing=1
  fi
done < <(
  find "$ROOT" \
    \( -name node_modules -o -name dist -o -name build -o -name .git \
       -o -name .worktrees \
       -o -path "$ROOT/data" -o -path "$ROOT/monitoring/.bin" \
       -o -path "$ROOT/monitoring/.data" -o -name "__snapshots__" \) -prune -o \
    -type f \( -name "*.js" -o -name "*.ts" -o -name "*.tsx" -o -name "*.cjs" \
       -o -name "*.mjs" -o -name "*.py" -o -name "*.sh" -o -name "*.css" \) \
    ! -name "*.min.js" ! -path "$ROOT/wiki/i18n-content.js" ! -path "*/wiki/i18n-content.js" -print
)

if [ "$missing" -eq 0 ]; then
  echo "✔ All applicable files carry the authorship header."
fi
exit "$missing"
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall