pushing
Skill2 starsChanged 41 days agoMITView on GitHub
Use before pushing, force-pushing, marking ready for review, or claiming checks pass on a harness-deepseek-harness branch, and immediately after gh stack sync publishes rewritten branches, to select the smallest tests and checks that cover the outgoing or just-published diff without reflexively running the full repository suite.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- hwang-yeonsu/re-harmoniztheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- hwang-yeonsu/re-harmoniz★ 0same name
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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/rfcs/AGENTS.mdAGENTS.md
- .agents/rfcs/archived/AGENTS.mdAGENTS.md
- .agents/rfcs/implemented/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- archiving-rfcsSkill
- documentingSkill
- editing-proseSkill
- finding-simplificationsSkill
- merging-stacked-prsSkill
- reviewingSkill
- translating-docsSkill
- trimming-cot-leakageSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 12 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Verify the live PR base or stack parent, fetch that ref, and inspect the complete scope against it.
- Very specific: line 31
Python behavior: run the owning pytest file or focused test name (uv run pytest tests/<behavior>.py -k <name>).
- Very specific: line 32
Documentation: run uv run hdsh pairing verify.
- Very specific: line 33
Typed source: run uv run basedpyright when the diff touches annotations the checker owns in src/ or tests/.
- Very specific: line 34
Packaging or entry points: after changing pyproject.toml, prek.toml, or .pre-commit-hooks.yaml, run uv sync and the owning smoke for each …
- Distinctive: line 37
Do not manually repeat a passing check merely because commit or push follows.
- Distinctive: line 51
Run the complete local approximation only when the user explicitly requests it, while diagnosing a CI failure, or when the change spans the …
- Distinctive: line 57
After any rewritten push, fetch the live heads again and re-audit unresolved review threads, approvals, mergeability, and checks.
- Distinctive: line 65
Run the relevant evidence selected by this skill for each affected layer.
- Distinctive: line 66
Keep every PR unmerged and report validation as pending until all selected checks pass.
- Distinctive: line 68
If post-sync evidence fails, leave the lease-protected published heads in place, repair the failure, validate the repair, and publish the …
- Distinctive: line 72
If a relevant check fails before an ordinary push, stop and fix or explain the blocker.
- Distinctive: line 74
If a failure looks environment-specific, prove it:
- Distinctive: line 78
Prefer fixing cross-platform nondeterminism when the check is required.
- Distinctive: line 85
Run the selected relevant checks once.
- Distinctive: line 86
Commit normally and inspect any files changed by the ruff fixers before continuing.
- Very specific: line 88
Verify the remote ref matches local HEAD.
- Very specific: line 102
When gh pr checks reports "no checks reported" and /actions/runs?head_sha=<sha> returns total_count: 0, read mergeability before suspecting …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pushing harness-deepseek-harness branches
Use this skill to run relevant local evidence once before a harness-deepseek-harness push. The sole ordering exception is gh stack sync, which may publish a cascading rebase before the rewritten layers can be validated; validate them immediately afterward and do not merge until the evidence passes. Hooks are worktree-local (install them with uv run hdsh worktree install) and intentionally narrow: pre-commit fixes staged lint and format with ruff, checks staged whitespace, verifies staged pairing records, and runs the RFC format and frozen-archive gates; pre-push runs only basedpyright. CI owns exhaustive coverage and the platform matrix.
Inspect the outgoing change
- Confirm the checkout and branch.
git status --short --branch
git rev-parse --show-toplevel- Verify the live PR base or stack parent, fetch that ref, and inspect the complete scope against it.
uv run hdsh scope --base <merge-base-ref>The command never guesses or fetches a base. Supply the ref verified from current remote or stack state; use --head <ref> when inspecting a commit other than HEAD. Its versioned JSON records committed paths relative to the resolved merge base, while staged, unstaged, and untracked paths describe the current worktree. After merging a changed base, rerun the report, reassess which behavior the combined scope can affect, and rerun only checks invalidated by the merge.
Select relevant evidence
There is no universal local baseline beyond the hooks. Every behavior change needs the narrowest available test or purpose-built check that would fail for its regression; add broader checks only for surfaces the diff actually reaches.
- Python behavior: run the owning pytest file or focused test name (
uv run pytest tests/<behavior>.py -k <name>). Add adjacent test files when a shared contract changes; leave the full suite to CI unless the change is genuinely cross-cutting or the user requests it. - Documentation: run
uv run hdsh pairing verify; re-record a reviewed pair withuv run hdsh pairing record <pair>. Decision records under.agents/rfcs/additionally runuv run hdsh rfc verify. - Typed source: run
uv run basedpyrightwhen the diff touches annotations the checker owns insrc/ortests/. - Packaging or entry points: after changing
pyproject.toml,prek.toml, or.pre-commit-hooks.yaml, runuv syncand the owning smoke for each changed console script (for exampleuv run hdsh scope --base origin/mainor the focused tests). - Style beyond staged files: the pre-commit fixers cover staged files only; run
uv run ruff check .anduv run ruff format --check .when relevant files are not yet staged.
Do not manually repeat a passing check merely because commit or push follows. In particular, do not run basedpyright immediately before pushing solely to duplicate the pre-push hook.
Focus unit coverage on the affected source
Test selection and coverage selection are separate. A pytest path or -k filter chooses which tests run, while the repository configuration measures every src/hdsh/** module and fails the run under 100% branch coverage. A focused subset therefore suspends the aggregate threshold only to inspect the affected modules, never to bless them:
uv run pytest tests/test_<behavior>.py --cov-fail-under=0 --cov-report=term-missingName both the owning tests and the source modules whose coverage those tests must prove, and read the report for exactly those modules. The unmodified uv run pytest remains the gate that must pass before the change lands, and CI re-runs it on the full matrix. Do not delete branches, exclude modules from measurement, or weaken assertions merely to hide an uncovered affected file; add the missing owning tests instead.
Full local rehearsal
Run the complete local approximation only when the user explicitly requests it, while diagnosing a CI failure, or when the change spans the repository so broadly that no narrower set is credible. The full local set is uv run ruff check ., uv run ruff format --check ., uv run basedpyright, and uv run pytest.
Protect history-rewriting pushes
Rebase is allowed for standalone and stacked PR branches, including after review. Before a standalone history rewrite, fetch the current remote branch and record its exact OID; publish with --force-with-lease=<branch>:<observed-oid> so a concurrent update aborts the push. gh stack push and gh stack sync supply lease protection for their managed branches. Raw --force is never allowed.
After any rewritten push, fetch the live heads again and re-audit unresolved review threads, approvals, mergeability, and checks. Commit hashes and inline-comment anchors from before the rewrite are not current evidence.
Post-sync validation
gh stack sync fetches, cascade-rebases, and pushes as one operation, so it cannot place local validation between rewrite and publication. Before running it, require a clean worktree and record the official stack order and exact remote heads. After it returns:
- Re-query every branch head and the official GitHub stack order.
- Inspect the changed scope of every rewritten layer against its live PR base.
- Run the relevant evidence selected by this skill for each affected layer.
- Keep every PR unmerged and report validation as pending until all selected checks pass.
If post-sync evidence fails, leave the lease-protected published heads in place, repair the failure, validate the repair, and publish the correction. Do not claim the sync made the stack ready merely because the command succeeded.
Handle failures
If a relevant check fails before an ordinary push, stop and fix or explain the blocker. Do not push and hope CI differs. For the post-sync exception, block the merge and follow the repair procedure above.
If a failure looks environment-specific, prove it:
- Record the exact command, failing test, and platform-specific mismatch.
- Confirm the relevant non-platform evidence.
- Prefer fixing cross-platform nondeterminism when the check is required.
- Bypass a local hook only when the user explicitly asks or agrees, and report exactly what failed and why CI is expected to differ.
Push procedure
For ordinary and standalone rebase pushes:
- Run the selected relevant checks once.
- Commit normally and inspect any files changed by the ruff fixers before continuing.
- Push normally, or use the exact lease for an authorized rewritten branch, so the pre-push basedpyright hook runs.
- Verify the remote ref matches local
HEAD.
git rev-parse HEAD origin/$(git branch --show-current)For GitHub PRs, inspect remote CI after the push:
gh pr checksReport pending checks as pending. Inspect failures before attributing them to the branch or the environment.
When gh pr checks reports "no checks reported" and /actions/runs?head_sha=<sha> returns total_count: 0, read mergeability before suspecting the push or a dropped GitHub event:
gh pr view <number> --json mergeable,mergeStateStatusGitHub creates no pull_request workflow runs while a PR is CONFLICTING/DIRTY, so the absent signal is the conflict, not infrastructure. Resolving the conflict is the only fix; empty commits, --allow-empty pushes, draft/ready toggles, and revert-and-restore bounces all leave total_count at zero and add junk history. Confirm the conflicting paths with git merge-tree --write-tree HEAD origin/<base> when the branch cannot be merged locally yet.
For gh stack sync, use the post-sync validation sequence instead of pretending the ordinary order was possible.
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.

