agentleFS
sasuketoriisasuketorii/rev_harness_public/.agents/skills/naming-normalization-guard/SKILL.md

naming-normalization-guard

Skill0 starsChanged 3 months agoApache-2.0View on GitHub

Use when adding, importing, renaming, or reorganizing Skills and knowledge packs in this repository. Enforces the project naming policy, updates internal references, preserves required skill entrypoint filenames, and checks for stale paths before commit.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run git status --short --branch and identify unrelated user changes.

    line 53
  2. Distinctive:

    Update internal Markdown references and command examples.

    line 56
  3. Distinctive:

    Update root README.md if a new top-level Skill or knowledge pack was added.

    line 57
  4. Very specific:

    Add or update .gitignore only for generated or tool-local files.

    line 58
  5. Very specific:

    Run stale-name checks with rg.

    line 59
  6. Distinctive:

    Run lightweight script checks when scripts were renamed.

    line 60
  7. Distinctive:

    Use a targeted search after every rename:

    line 65
  8. Distinctive:

    Do not bundle unrelated user edits into the rename commit.

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Naming Normalization Guard

この Skill は、REV DevSkills に新しい Skill / knowledge pack / deploy guard を追加したり、既存ファイルをリネームするときに使う。

目的は、名前だけをきれいにすることではない。Codex / Claude Code が読み込む入口、README のコマンド例、内部参照、インストール先、更新プロンプトまで含めて、壊れない形で名前を統一する。

Rules

  • ディレクトリと通常ファイルは kebab-case に統一する。
  • README.md、SKILL.md、AGENTS.md は規約ファイルなのでリネームしない。
  • references/、scripts/、prompts/ はそのままのディレクトリ名を使う。
  • *_knowledge_pack_vX_Y_Z は <language>-skills-knowledge-pack にする。
  • payloadcms のように詰まった製品名は、読みやすい場合だけ payload-cms のように分割する。
  • version はファイル名に残す必要がある監査レポートだけ v0.1.2 のように残す。
  • .DS_Store、__pycache__/、.pyc、.claude/ は追跡しない。

Rename Pattern

goskills_knowledge_pack_v0_1_1
  -> go-skills-knowledge-pack

typescriptskills_knowledge_pack_v0_1_1
  -> typescript-skills-knowledge-pack

rustskills_knowledge_pack_v0_1_2
  -> rust-skills-knowledge-pack

payloadcms-deploy-guard
  -> payload-cms-deploy-guard

Within each pack:

rustskills_master.md
  -> rust-skills-master.md

rustskills_sources.md
  -> rust-skills-sources.md

browser_automation_cdp.md
  -> browser-automation-cdp.md

Required Workflow

  1. Run git status --short --branch and identify unrelated user changes.
  2. List candidate paths with find . -maxdepth 4 -type f | sort.
  3. Rename directories and files with mv.
  4. Update internal Markdown references and command examples.
  5. Update root README.md if a new top-level Skill or knowledge pack was added.
  6. Add or update .gitignore only for generated or tool-local files.
  7. Run stale-name checks with rg.
  8. Run lightweight script checks when scripts were renamed.
  9. Show the user the result before commit or push.

Stale Name Checks

Use a targeted search after every rename:

rg -n "goskills_|typescriptskills_|rustskills_|payloadcms-deploy-guard|source_links|source_manifest|data_sources|browser_automation|pack_audit|runtime_toolchain|api_crawler|ai_agent" .

Expected remaining matches are allowed only when they are package names, URLs, historical text, or generated artifact names that intentionally keep the old token. Everything else should be updated.

Commit Boundary

Do not bundle unrelated user edits into the rename commit. If files were already modified before the rename work, either leave them unstaged or explicitly call them out before commit.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.