agentleFS
Sign inStart free
SummerSecSummerSec/SumSec-Skills/semantic-linter/CLAUDE.md

SumSec-Skills / semantic-linter

CLAUDE.md8 starsChanged 18 days agoApache-2.0View on GitHub

This directory packages SummerSec/semantic-linter as a standalone plugin in the SumSec-Skills marketplace. Do not edit synced component directories under semantic-linter/ directly. Update the pinned submodule commit, re-copy root files if needed, and run the repository sync script instead. When the upstream inventory changes, synchronize the plugin directory and update the root README plus Claude, Codex, Cursor, OpenCode, OpenClaw, Hermes, DSH, and Pi discovery metadata in the same change. Semantic-Linter is more than skills:

The file

We split this CLAUDE.md into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not edit synced component directories under semantic-linter/ directly.

    line 21
  2. Distinctive:

    When the upstream inventory changes, synchronize the plugin directory and update the root README plus Claude, Codex, Cursor, OpenCode, …

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
CLAUDE.md

Semantic-Linter Plugin

This directory packages SummerSec/semantic-linter as a standalone plugin in the SumSec-Skills marketplace.

Source And Sync

  • Canonical upstream: semantic-linter-upstream/
  • Synchronized components:
    • skills/
    • hooks/
    • commands/
    • lib/
    • bin/
    • scripts/
    • references/
  • Root files copied from upstream on packaging updates:
    • semantic-rules.md
    • package.json
  • Mapping: .claude/skills/sync-skills/scripts/skill-map.json

Do not edit synced component directories under semantic-linter/ directly. Update the pinned submodule commit, re-copy root files if needed, and run the repository sync script instead.

Plugin Metadata

  • Claude Code: .claude-plugin/plugin.json
  • Codex: .codex-plugin/plugin.json
  • Cursor: .cursor-plugin/plugin.json
  • Upstream version source: semantic-linter-upstream/package.json

When the upstream inventory changes, synchronize the plugin directory and update the root README plus Claude, Codex, Cursor, OpenCode, OpenClaw, Hermes, DSH, and Pi discovery metadata in the same change.

Runtime Notes

Semantic-Linter is more than skills:

  • Hooks: SessionStart / SubagentStart / UserPromptSubmit / PreToolUse / PostToolUse
  • Commands: /stl-init, /stl-lexicon, /stl-rules
  • CLI: node bin/scan.js (package bin name semantic-lint)
  • Default mode: guarded

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.

Check your setup, free