file-header-guardian
Add Consistent File Header Comments
Teams lose context when source files lack clear purpose and dependency notes. This skill guides Claude, Codex, and Claude Code to add concise header comments for supported code files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "file-header-guardian" from https://skillstore.io/skills/dimon94-file-header-guardian.md and its manifest at https://skillstore.io/api/skills/dimon94-file-header-guardian/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "file-header-guardian". A new user service file is created without a header.
Expected outcome:
The response adds a concise header that names the database dependency, service operations, and module role.
Using "file-header-guardian". A modified Python module now calls a cache helper but the header is old.
Expected outcome:
The response updates the dependency note and keeps the module purpose aligned with the implementation.
Using "file-header-guardian". A change set includes a stylesheet, a generated declaration file, and a shell script.
Expected outcome:
The response skips exempt files and adds the contract header only to the script file.
Security Audit
SafeAll seven static findings are false positives caused by Markdown code fences in SKILL.md. The skill provides file header comment templates and exemptions, with no evidence of command execution, prompt injection, data exfiltration, or malicious intent.
Risk Factors
⚙️ External commands (7)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/dimon94-file-header-guardian/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dimon94-file-header-guardian?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dimon94-file-header-guardian?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dimon94-file-header-guardian/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dimon94-file-header-guardian.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Dimon94. (2026). file-header-guardian security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dimon94-file-header-guardian/audits/8BibTeX citation
@techreport{dimon94-dimon94-file-header-guardian-2026,
author = {Dimon94},
title = {file-header-guardian security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/dimon94-file-header-guardian/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "file-header-guardian security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Dimon94"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/dimon94-file-header-guardian/audits/8"
identifiers:
- type: other
value: "skillstore:dimon94-file-header-guardian:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Standardize New Services
Add purpose and dependency notes when creating new application service files.
Review Documentation Drift
Check that file headers still match behavior after code changes.
Keep Agent Work Traceable
Help AI coding sessions leave concise context for future maintainers.
Try These Prompts
Create this source file and add the required @input, @output, and @pos header comment before the implementation.
Review this changed file and update its header comment so the dependencies, exports, and system role are accurate.
Review these changed files and add headers only where the skill applies. Skip config, style, generated, and dependency files.
Audit this feature folder, update applicable file headers, and align the related directory CLAUDE.md notes with the current file roles.
Best Practices
- Write headers after understanding the real dependencies and exported behavior.
- Keep each header short enough to maintain during normal code review.
- Update directory documentation when file roles change materially.
Avoid
- Do not add generic headers that restate the filename only.
- Do not force headers into exempt generated, config, style, or dependency files.
- Do not leave the header unchanged after changing dependencies or module responsibility.