agentleFS
Sign inStart free
gocronx-teamgocronx-team/gocron/.agents/skills/verify/SKILL.md

verify

Skill808 starsChanged 3 months agoMITView on GitHub

Reproduce the complete gocron CI pipeline locally and report every result. Use before commits, pull requests, merges, tags, or releases; when asked to verify, check, lint, test, build, or determine whether the repository is ready to ship.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Run from the repository root.

    line 8
  2. Distinctive:

    Do not modify source files when the user only asks to verify or report.

    line 14
  3. Distinctive:

    If the user also asks to fix failures, make the smallest relevant fixes and rerun every affected check.

    line 15
  4. Distinctive:

    Do not discard, overwrite, or attribute pre-existing changes to this work.

    line 17
  5. Distinctive:

    Do not stop after the first failure.

    line 21
  6. Very specific:

    Run gofmt -l .. Any listed Go file is a failure.

    line 24
  7. Very specific:

    Run golangci-lint run ./....

    line 27
  8. Distinctive:

    If dependencies or tools are missing, clearly distinguish an environment failure from a code failure.

    line 37

“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

Verify gocron

Run from the repository root. Treat .github/workflows/ci.yml as the source of truth if it differs from this skill.

Preserve the working tree

  • Inspect git status --short before running checks.
  • Do not modify source files when the user only asks to verify or report.
  • If the user also asks to fix failures, make the smallest relevant fixes and rerun every affected check.
  • Do not discard, overwrite, or attribute pre-existing changes to this work.

Run all checks

Do not stop after the first failure. Record the exit status and useful output for each independent check.

  1. Run gofmt -l .. Any listed Go file is a failure; do not run gofmt -w unless fixes were requested.
  2. Run go vet ./....
  3. Run golangci-lint run ./.... CI uses v2.12.2; report a missing or incompatible local version instead of silently substituting another version.
  4. Run go test -race -coverprofile=coverage.out ./....
  5. In web/gocronx-admin, run these as separate checks so one failure does not hide the others:
    • pnpm build-only
    • pnpm exec vue-tsc --noEmit
    • pnpm lint
  6. Run docker build -f Dockerfile.gocron -t gocron:ci ..

If dependencies or tools are missing, clearly distinguish an environment failure from a code failure. Installing tools or packages may require network access; obtain any required approval and use the versions pinned by the repo or CI. Do not claim the check passed when it was skipped.

Report

End with a compact table containing each check, pass/fail/skipped status, and the actionable error. Include exact file:line locations where available. Mention whether coverage.out or generated frontend files changed the working tree.

Say the repository is ready to commit, merge, or release only when every required check passes, including the Docker build.

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. react/react★ 252ksame name
    2. facebook/react★ 252ksame 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-claude-sisyphus★ 40ksame name
    8. Yeachan-Heo/oh-my-claudecode★ 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.

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