agentleFS
Sign inStart free
PMDevSolutionsPMDevSolutions/Flavian/.claude/skills/lint/SKILL.md

lint

Skill19 starsChanged 12 days agoMITView on GitHub

Run this repository's linters and standards checks (WordPress PHPCS, the security and performance scans, the Claude Code conformance check, documentation counts, commitlint, the GUI lint) and report what failed. Keywords: lint, phpcs, coding standards, security scan, conformance, commitlint

80 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use query, ingest 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.
  • ArtemXTechSkill

    query

    Query data from this vault. USE WHEN user asks about projects, clients, tasks, daily notes. Use grep to extract frontmatter - do NOT read full files.

    Also in 17 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 26 projects that use this

  • PydanticSkill

    coverage

    Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.

    Also in 4 projects that use this

  • seongjaeryuSkill

    save

    Complete and save your current thinking to Bindly

    Also in 5 projects that use this

  • BugRogerSkill

    project

    Project lifecycle management. Dispatches to Ada.

    Also in 4 projects that use this

  • AnthropicSkill

    digest

    Generate a daily or weekly digest of activity across all connected sources. Use when catching up after time away, starting the day and wanting a summary of mentions and action items, or reviewing a week's decisions and document updates grouped by project.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 67 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run every applicable check and keep going after a failure.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 67 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

/lint — run the repository's checks

Target: $ARGUMENTS. A theme or plugin directory (themes/flavian-shop, plugins/my-block), or all. With no argument, check every directory under themes/ and plugins/ that has a style.css or a plugin header.

This repo is WordPress (PHP), Node and shell. There is no Python here; the Python linters an older copy of this command described never applied.

What runs

CheckCommandCatches
WordPress coding standards./scripts/wordpress/check-coding-standards.sh <path>PHPCS with the WordPress rulesets (set up once with ./scripts/wordpress/setup-phpcs.sh)
Security scan./scripts/wordpress/security-scan.sh <path>unescaped output, unsanitised input, missing nonces and capability checks, raw SQL
Performance./scripts/wordpress/check-performance.sh <path>unoptimised assets, unconditional enqueues, expensive queries
Theme structure./scripts/validate-theme.sh <theme>theme.json, templates, parts, root-level layout
Claude Code configurationnode scripts/claude-code-conformance.jsretired tool names, bad frontmatter, dead hooks, plugin manifest drift
Documentation countsbash scripts/check-doc-counts.sh"N agents" / "N skills" claims that drifted from disk
Commit messagespnpm lint:commitsConventional Commits since origin/main (release-please reads them)
GUIpnpm gui:lint && pnpm gui:typecheckpackages/gui only; run when GUI files changed

Steps

  1. Resolve the target directories. Skip a PHP check for a directory with no PHP.
  2. Run every applicable check and keep going after a failure; capture each exit code.
  3. Report a table: check, pass or fail, the first failing lines, the exact command to re-run.
  4. Fix nothing silently. List the fixes you would make; apply them only if the user asked to fix lint, and re-run the failed checks afterwards.

A hook already reminds you to run the full gate after a standards check passes (post-bash-reminders.sh build-qa); /lint all is that gate.

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