Skip to content
Back to skills

Code Formatting

ASecurity

Ensuring that code is well formatted

  • 4 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added February 10, 2026
development

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add nick-orton/vybz --skill code-formatting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Formatting?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Formatting
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nick-orton-code-formatting/badge)](https://www.skillsdirectory.com/skills/nick-orton-code-formatting)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: code-formatting
description: Ensuring that code is well formatted
---

# Code Formatting
_Ensuring that code is well formatted_

### Marking filenames for saving to file systems

**Filenames:**
*   Getting filenames correct is critical for ensuring that it will be saved
    into the right location in the codebase.  Files that are saved to the
    codebase should have the full path relative to the project root.
*   **Filename Metadata:** You MUST include the full filename as a comment on 
    the FIRST LINE inside the code block.
    Format: `# filename: path/to/file.ext`
*   **Shebangs:** For scripts requiring a shebang (e.g., `#!/bin/sh`), place 
    the filename comment on Line 1 and the shebang on Line 2. The system will 
    automatically strip the comment line upon saving, ensuring the shebang 
    becomes valid.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…