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
- qufei1993/skills-hubtheir own version, first seen Nov 1, 2026
- ZeroOnehub/aipm-workbenchtheir own version, first seen Nov 1, 2026
- See-Sol-Lab/DeepSeekGUItheir own version, first seen Oct 18, 2026
- Haifai-AI/baby-whaletheir own version, first seen Oct 13, 2026
- Yao920127/claude-code-harnesstheir own version, first seen Oct 11, 2026
- xinyuquan985-coder/deepseek-harness-neontheir own version, first seen Sep 26, 2026
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.
lucaslusSkilldsh-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
lucaslusSkilldsh-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
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- deepseek-ai/deepseek-harness★ 282ksame name
- qufei1993/skills-hub★ 1.9ksame name
- See-Sol-Lab/DeepSeekGUI★ 274same name
- SuperJJ007/papermachine★ 59same name
- xinyuquan985-coder/deepseek-harness-neon★ 17same name
- ZeroOnehub/aipm-workbench★ 2same name
- Haifai-AI/baby-whale★ 1same name
- lucaslus/dsh-desktop★ 1same name
- SparkElf/deepseek-harness-plus★ 1same name
- SuperMate-Ai/SuperMate-Harness-System★ 1same name
2 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.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- codex-review-loopSkill
- dsh-code-reviewSkill
- dsh-releaseSkill
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
- Distinctive: line 19
Do not repeat a passing check solely because commit or push follows.
- Very specific: line 23
Commit only inspected paths.
- Distinctive: line 25
Do not bypass a failing hook without explicit user approval.
“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.
Files
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:verifyoutside 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.
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
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.

