agentleFS
Sign inStart free
BingZi-233BingZi-233/check-cx/.claude/skills/verify/SKILL.md

verify

Skill636 starsChanged 3 months agoMITView on GitHub

Verify Check CX changes by running the right local checks and manually exercising UI behavior when relevant.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 3

    Distinctive

    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:

    Use this skill when validating local changes before reporting them complete.

    line 6
  2. Very specific:

    Run pnpm lint for any code change.

    line 8
  3. Very specific:

    Run pnpm build when changes touch routing, server code, dependencies, config, Docker/deployment behavior, or anything that can affect …

    line 9
  4. Distinctive:

    If Supabase schema, migrations, or provider configuration behavior changed, state which migration/config path was checked and whether a …

    line 11
  5. Distinctive:

    If a check cannot be run because credentials or environment are missing, say exactly what is missing instead of claiming verification …

    line 12

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

Use this skill when validating local changes before reporting them complete.

  1. Run pnpm lint for any code change.
  2. Run pnpm build when changes touch routing, server code, dependencies, config, Docker/deployment behavior, or anything that can affect production output.
  3. For UI or frontend behavior changes, start the app with pnpm dev, open the affected route in a browser, exercise the golden path and obvious edge cases, and check the page for visual regressions.
  4. If Supabase schema, migrations, or provider configuration behavior changed, state which migration/config path was checked and whether a staging database replay is still needed.
  5. If a check cannot be run because credentials or environment are missing, say exactly what is missing instead of claiming verification succeeded.

Download now (ZIP)

  • Other versions188 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 188

    1. facebook/react★ 252ksame name
    2. react/react★ 251ksame name
    3. garrytan/gstack★ 139ksame name
    4. oven-sh/bun★ 96ksame name
    5. anthropics/financial-services★ 41ksame name
    6. anthropics/financial-services-plugins★ 41ksame name
    7. Yeachan-Heo/oh-my-claudecode★ 40ksame name
    8. Yeachan-Heo/oh-my-claude-sisyphus★ 40ksame name
    9. anthropics/claude-quickstarts★ 19ksame name
    10. NVIDIA-NeMo/NeMo★ 19ksame name

    178 more not listed

    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.

  • Used alongsideProjects with it also use build-fix, external-context 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.
    • diego-tobalinaSkill

      build-fix

      Fix build and compilation errors systematically. Run when build fails.

      Also in 6 projects that use this

    • Jurel89Skill

      external-context

      Invoke parallel document-specialist agents for external web searches and documentation lookup

      Also in 3 projects that use this

    • TheKREATORSSkill

      instinct-export

      Export instincts from project/global scope to a file

      Also in 3 projects that use this

    • TheKREATORSSkill

      instinct-import

      Import instincts from file or URL into project/global scope

      Also in 3 projects that use this

    • AviadPSkill

      risk-assess

      Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).

      Also in 3 projects that use this

    • Jurel89Skill

      configure-notifications

      Wire Telegram / Discord / Slack notifications for copilot-omni run events (start, progress, completion, error)

      Also in 3 projects that use this

    • +2 more from Jurel89
  • In this repository9 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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