agentleFS
nodealchemynodealchemy/powernode-platform/.claude/skills/audit/SKILL.md

audit

Skill4 starsChanged 18 days agoMITView on GitHub

Run comprehensive codebase quality and pattern compliance audit

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use delight, teach-impeccable and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • HK-hubSkill

    delight

    Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful. Use when the user asks to add polish, personality, animations, micro-interactions, delight, or make an interface feel fun or memorable.

    Also in 32 projects that use this

  • HK-hubSkill

    teach-impeccable

    One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.

    Also in 19 projects that use this

  • zwy123zwySkill

    normalize

    将用户随意输入的提示词规范化为结构清晰、便于大模型执行的标准化提示词。适用于需要整理、统一提示词格式时调用。

    Also in 19 projects that use this

  • SkillPilotCHSkill

    level-up

    Eine Automatisierung pro Woche finden, scopen, shippen. Output landet als proposed-Eintrag in cadence.md mit konkreten Implementations-Schritten.

    Also in 12 projects that use this

  • ww-w-aiSkill

    pm-discovery

    PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.

    Also in 3 projects that use this

  • +7 more from HK-hub

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 175 edited versions we read keep these.

  • 4

    Distinctive

    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. Distinctive:

    Run quality checks and report results.

    line 11
  2. Distinctive:

    Run applicable checks sequentially.

    line 23
  3. Very specific:

    Check all .rb files changed since last commit:

    line 44
  4. Distinctive:

    Verify all Ruby classes load without errors:

    line 54
  5. Distinctive:

    If any check has issues, list the specific files/errors below the table.

    line 92

“Common” is measured: kept by at least 6 in 10 of the 175 edited versions of this file we could read. “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

Codebase Quality Audit

Run quality checks and report results. Accept an optional focus argument to limit scope.

Focus Areas

  • all (default) — run everything
  • backend — Ruby checks only (steps 1, 4, 5, 6)
  • frontend — Frontend checks only (steps 3, 7, 8)
  • types — TypeScript type check only (step 3)
  • patterns — Pattern validation only (steps 1, 2)

Checks

Run applicable checks sequentially. Capture output from each.

The harness does not export $PROJECT_DIR, and shell state does not carry between Bash calls, so each command below defines it first as the repository root.

1. Pattern Validation

PROJECT_DIR="$(git rev-parse --show-toplevel)"; cd $PROJECT_DIR && ./scripts/pattern-validation.sh

2. Quick Pattern Check

PROJECT_DIR="$(git rev-parse --show-toplevel)"; cd $PROJECT_DIR && ./scripts/quick-pattern-check.sh

3. TypeScript Type Check

PROJECT_DIR="$(git rev-parse --show-toplevel)"; cd $PROJECT_DIR/frontend && npx tsc --noEmit 2>&1

4. Ruby Syntax Check

Check all .rb files changed since last commit:

PROJECT_DIR="$(git rev-parse --show-toplevel)"; cd $PROJECT_DIR/server && git diff --name-only --relative HEAD -- '*.rb' | xargs -I{} ruby -c {} 2>&1

Also check untracked .rb files:

PROJECT_DIR="$(git rev-parse --show-toplevel)"; cd $PROJECT_DIR/server && git ls-files --others --exclude-standard -- '*.rb' | xargs -I{} ruby -c {} 2>&1

5. Rails Eager Load Check (backend only)

Verify all Ruby classes load without errors:

PROJECT_DIR="$(git rev-parse --show-toplevel)"; cd $PROJECT_DIR/server && bundle exec rails runner "Rails.application.eager_load!; puts 'Eager load OK'" 2>&1

6. Frozen String Literal Pragma

Scan for Ruby files missing the pragma:

PROJECT_DIR="$(git rev-parse --show-toplevel)"; grep -rL "frozen_string_literal: true" $PROJECT_DIR/server/app/ --include="*.rb" | head -20

7. Console.log Scan

PROJECT_DIR="$(git rev-parse --show-toplevel)"; grep -rn "console\.log" $PROJECT_DIR/frontend/src/ --include="*.ts" --include="*.tsx" | head -20

8. Hardcoded Color Scan

PROJECT_DIR="$(git rev-parse --show-toplevel)"; grep -rn "bg-\(red\|blue\|green\|yellow\|gray\|slate\|zinc\|neutral\|stone\)" $PROJECT_DIR/frontend/src/ --include="*.tsx" | grep -v "theme" | head -20

Output

Present results as a summary table:

| Check                  | Status | Issues |
|------------------------|--------|--------|
| Pattern Validation     | ✅/❌  | count  |
| Quick Pattern Check    | ✅/❌  | count  |
| TypeScript Types       | ✅/❌  | count  |
| Ruby Syntax            | ✅/❌  | count  |
| Rails Eager Load       | ✅/❌  | count  |
| Frozen String Literal  | ✅/❌  | count  |
| Console.log            | ✅/❌  | count  |
| Hardcoded Colors       | ✅/❌  | count  |

If any check has issues, list the specific files/errors below the table.

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.