agentleFS
pawacapawaca/dsh-edge/.agents/skills/dsh-pre-push-checks/SKILL.md

dsh-pre-push-checks

Skill30 starsChanged 37 days agoMITView on GitHub

Select and run the smallest sufficient dsh-edge checks before pushing, force-pushing, marking a PR ready, or claiming a branch is validated. Use for Worker runtime, installer, Edge client, standalone assembly, documentation, release, or governance changes without reflexively repeating the complete suite.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dsh-doc-site-sync and dsh-doc-standards.

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.
  • lucaslusSkill

    dsh-doc-site-sync

    Use when publishing, updating, moving, or removing DeepSeek Harness documentation website pages; editing website/docs.ts mappings or navigation; diagnosing a page missing from the VitePress site; fixing projected documentation links; or running the docs:dev, docs:check, and doc-sync workflow after website-content changes.

    Also in 5 projects that use this

  • lucaslusSkill

    dsh-doc-standards

    Use when writing, moving, reviewing, or auditing documentation in the deepseek-harness repo — choosing hierarchy and detail, separating tutorials from references, checking tutorial progression, trimming doc slop, responding to a verify-doc-budgets failure, or requests like "improve the docs", "audit the docs", "where should this be documented", or "this doc is too long".

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    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. Distinctive:

    Do not repeat a passing check solely because commit or push follows.

    line 19
  2. Very specific:

    Commit only inspected paths.

    line 23
  3. Distinctive:

    Do not bypass a failing hook without explicit user approval.

    line 25

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

dsh-edge pre-push checks

Inspect git status --short --branch, verify the live PR base, and read the complete diff against its merge base. Classify changed files by owned surface before selecting evidence.

Select evidence

  • Runtime, storage, authentication, credentials, or protocol: run the focused unit file and the affected Direct/Dynamic integration path.
  • Edge client or visible output: run its focused test and the browser/runtime snapshot suite.
  • Standalone dependencies, patches, bundle configuration, or Web assembly: run the standalone build and verifier, then promote and start both exact prebuilt artifacts.
  • Installer, package files, or release automation: pack the npm artifact and run pack:verify outside the workspace; run workflow and publication tests.
  • Documentation, governance, or legal files: run pnpm run doc-sync; compare bilingual meaning manually.
  • Cross-cutting repository extraction or dependency changes: run pnpm run check, both standalone builds, integration, snapshots, and package verification.

Do not repeat a passing check solely because commit or push follows. CI owns the clean Linux checkout; local evidence owns failures that CI cannot reproduce, macOS behavior, and exact package contents.

Push safely

Commit only inspected paths. Push normally unless the user authorized a history rewrite; use --force-with-lease=<branch>:<observed-oid> for an authorized rewritten branch and never raw --force. Verify the remote ref equals local HEAD, then inspect the new CI and review phase.

Do not bypass a failing hook without explicit user approval. If a failure is environmental, record the exact command and evidence before proposing a bypass.

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.