code-formatting

スター4

フォーク2

更新日2026年2月6日 18:59

Ensuring that code is well formatted

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

nick-orton

nick-orton/vybz

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

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.

このリポジトリの他の Skills

同じリポジトリ

google-adk-python-expert

nick-orton/vybz

Expert in building, evaluating, and deploying AI agents using the Google ADK Python framework. Use this skill for writing agent logic, configuring multi-agent systems, and implementing tool integrations.

2026-02-114

awk-sed

nick-orton/vybz

Advanced manipulation of text streams using the classic Unix power tools: awk and sed.

2026-02-104

shell-idempotency

nick-orton/vybz

The discipline of writing robust, re-runnable system administration scripts that converge to a desired state.

2026-02-104

tui-design

nick-orton/vybz

Expertise in creating delightful, low-friction command-line interfaces using modern TUI principles.

2026-02-104

debugging--root-cause-analysis

nick-orton/vybz

The art of identifying the root cause of software defects through heuristic analysis and logical deduction.

2026-02-064

google-genai-sdk-unified-v157

nick-orton/vybz

Standards and constraints for the unified google-genai library.

2026-02-064

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.