agentleFS
Sign inStart free
PorabuildPorabuild/Poracode/.agents/skills/verify/SKILL.md

verify

Skill121 starsChanged 5 days agoApache-2.0View on GitHub

Runs Poracode's canonical pre-push check gate and reports exact commands and results. Use when asked to "verify", "run the checks", "make CI green", "fix all checks", "is this ready to push", or before committing, pushing, or marking a PR ready. Not for driving the live app (use interactive-testing) or reviewing code quality (use a review skill).

188 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use instinct-export, instinct-import 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.
  • 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

  • diego-tobalinaSkill

    build-fix

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

    Also in 6 projects that use this

  • AaravChadhaSkill

    secure

    Security review with a confidence gate - a finding exists only with a concrete exploit scenario and a high/medium/low confidence rating; everything else goes to a worth-hardening list, never inflated. Sweeps five surfaces: auth gates, secrets hygiene, injection and unsafe sinks, unsafe deserialization/crypto/transport, and LLM tool-use trust boundaries. Reports only, never fixes. Use when the user asks for a security review or to check vulnerabilities, secrets, or auth.

    Also in 3 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 10 projects that use this

  • +1 more from TheKREATORS

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 166 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Never weaken a check to get green: no skipping or deleting tests, no .skip/.only, no disabling lint rules, no loosening types, no raising …

    line 12
  2. Distinctive:

    Use for in-progress work and focused fixes.

    line 19
  3. Very specific:

    Run the nearby tests: the touched files' *.test.ts(x) plus tests for direct callers.

    line 28
  4. Very specific:

    Use bun run vitest run; Jest-only flags such as --runInBand do not exist here.

    line 32
  5. Distinctive:

    Run all four when asked to fix all checks, before marking a PR ready for review, or when the change crosses shared runtime, IPC, or build …

    line 37
  6. Distinctive:

    Add these when the change touches the matching area:

    line 49
  7. Very specific:

    Test shards: bun run test split 8 ways.

    line 73

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

The single gate to pass before pushing. Prove the change works with real checks, then report exactly what ran.

Rules

  • Never weaken a check to get green: no skipping or deleting tests, no .skip/.only, no disabling lint rules, no loosening types, no raising timeouts or thresholds. If a check is wrong, say so and fix it in a separate, explained change.
  • A syntax-only or compile-only pass is not verification of behavior; run the tests that exercise the change.
  • A failure you did not cause is still reported. Confirm it also fails on origin/master before calling it pre-existing.
  • Report every command with its result (pass/fail, test and file counts). State what you did not run and why.

Focused gate (default)

Use for in-progress work and focused fixes.

  1. Lint and format the touched files:
    bun run cross-env npm_lifecycle_event=lint bun lint --deny-warnings <files>
bun run cross-env npm_lifecycle_event=lint bun lint --type-aware --deny-warnings -c .oxlintrc.type-aware.json <files>
bun run cross-env npm_lifecycle_event=fmt bun fmt --check <files>
    The pinned Bun preview uses npm_lifecycle_event to select the built-in command instead of a same-named package script.
  2. Run the nearby tests: the touched files' *.test.ts(x) plus tests for direct callers.
    bun run vitest run <test paths or dirs>
    Use bun run vitest run; Jest-only flags such as --runInBand do not exist here.
  3. bun run typecheck --force.

Full gate

Run all four when asked to fix all checks, before marking a PR ready for review, or when the change crosses shared runtime, IPC, or build config:

bun run verify

verify runs fresh format, lint, and type checks, then the full unit suite. Under finalize, which merges only after CI passes on the exact pushed head, CI's sharded bun run test replaces the local run: run bun run checks --force locally plus the focused tests (focused gate step 2). Every other flow runs verify.

Other worktrees may be verifying on the same machine. bun run test and executed Turbo tasks queue behind scripts/heavy-run-gate.mjs (2 concurrent heavy runs per repository); a "waiting for a free slot" message is expected, not a hang. Do not bypass the gate or launch the full suite another way to jump the queue.

Conditional gates

Add these when the change touches the matching area:

  • Renderer strings (src/renderer): bun run i18n:extract reports 0 missing for every locale and every new msgstr is filled in all 12 non-English catalogs. See .agents/docs/i18n.md.
  • Persisted state, caches, manifests, wire/IPC protocols, deployed helpers: complete the audit in .agents/docs/versioning.md ("Required check for every change") and add the pre-upgrade regression test it calls for.
  • Remote protocol contract (src/shared/remote/contract/, protocol/remote/v3/): bun run protocol:remote:v3:check, then bun run vitest run --config tests/native-e2e/vitest.config.ts operationMap.test.ts (the operation-map hash lock).
  • Module boundaries or new cross-layer imports: bun run architecture:check.
  • Website (website/): bun run typecheck:website.
  • Perf-sensitive paths (CLI hook chain, remote protocol): bun run test:perf:cli-hook or bun run test:perf:remote.
  • Provider runtime behavior: bun run test:integration:providers when the provider CLIs are available; otherwise say it was not run.
  • Visible UI or app-shell behavior: a mock smoke run via the interactive-testing skill (bun run smoke:integration wraps its runner).
  • Smoke harness scripts (.agents/skills/interactive-testing/scripts/): node --test .agents/skills/interactive-testing/scripts/*.test.mjs.
  • TUI (tui/): bun run tui:typecheck and bun run tui:test.

CI map

.github/workflows/ci.yml runs these on every PR; docs-only changes (docs/, *.md) skip everything except Format.

  • Typecheck: bun run typecheck (Bun, all available cores; bun run typecheck:tsc is available for compiler comparison).
  • Lint: bun run lint, bun run architecture:check, smoke-harness and release/qualification script tests, and the native-e2e managedAppSession and operationMap locks.
  • Format: actionlint on workflows, then bun run fmt:check.
  • Canonical web build: bun run build:web.
  • Runtime dependencies: bun run build:electron plus the runtime-deps check in scripts/build-desktop-artifact.mjs.
  • Rust helper: cargo fmt, clippy, test, doc, deny.
  • TUI: bun run tui:typecheck and bun run tui:test.
  • Test shards: bun run test split 8 ways.
  • Perf suites: bun run test:perf:cli-hook and bun run test:perf:remote.

.github/workflows/native-ci.yml runs bun run protocol:remote:v3:check, the remote-v3 contract tests, and the Android and iOS builds when shared or native code changes.

Done when

  • The focused gate (or the full gate, when required) and every applicable conditional gate passed.
  • Any remaining failure is reported with its cause and evidence that it is pre-existing or out of scope.
  • The report lists each command run with its result, and each relevant check not run with the reason.

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