agentleFS
kuhlman-labskuhlman-labs/fishhawk/.agents/skills/frontend-check/SKILL.md

frontend-check

Skill9 starsChanged 5 days agoApache-2.0View on GitHub

Run the Fishhawk frontend CI checks. Use before pushing frontend changes, or when asked to format, lint, test or build the UI.

  • Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. yiyu-works/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    Run them in that order; format first is cheapest.

    line 30

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

Check the Web UI before pushing

CI runs pnpm format:check as its own gate. lint and typecheck do not catch formatting, so a change that passes those can still fail CI on prettier.

The repository helper scripts/check-frontend runs the installation and all five checks below. scripts/verify-change selects it for frontend inputs before the Go gate. Container prerequisites and exit 75 are documented in scripts/README.md § "Workflow verification".

1. Use the locked dependencies

cd frontend && pnpm install --frozen-lockfile --ignore-scripts

A stale local node_modules can carry a different prettier/eslint version than the lockfile. For example, local prettier 3.8 vs locked 3.9 produces opposite formatting verdicts. Reinstall before trusting, or overruling, a format result.

2. Run the checks (in frontend/)

CheckCommand
Format (CI gate)pnpm format:check, and fix with pnpm format
Lintpnpm lint
Typespnpm typecheck
Testspnpm test (vitest run, jsdom at https://localhost/ so __Host- cookies behave)
Buildpnpm build

Run them in that order; format first is cheapest. After pnpm format, re-run git diff --stat so the formatting changes are committed together with the real ones.

3. Known traps

  • Inside a run worktree (.git/fishhawk-worktrees/run-*), vitest can fail with a misleading Cannot find module '/src/test-setup.ts'. That's Vite's **/.git/** fs-deny rule, handled by frontend/vite-fs-deny.ts. Don't "fix" it by making setupFiles absolute.
  • Dev server: make dev-frontend (:5173, proxies /v0 to fishhawkd on :8080). It needs the stack up; see the deploy-local skill.

Report

Pass/fail per check, with the first error verbatim, plus any files pnpm format rewrote.

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.