publish-verified-github-change
Skill1 starsChanged 2 months agoMITView on GitHub
Commit, push, open or update a PR, follow CI, or merge an authorized change, publishing only an exact reviewed snapshot behind a frozen remote operation. Implementation grants no remote authority.
In this repository21 other files it gives its agents.
- change-production-data-safelySkill
- craft-contextual-uiSkill
- diagnose-root-causesSkill
- engineer-code-changeSkill
- engineer-reliable-data-pipelinesSkill
- engineer-secure-systemsSkill
- evaluate-agent-behaviorSkill
- handle-sensitive-data-safelySkill
- infer-intent-before-codingSkill
- migrate-contracts-safelySkill
- operate-production-safelySkill
- orchestrate-long-running-workSkill
- plan-decision-complete-changeSkill
- ponytailSkill
- release-production-changesSkill
- respond-to-production-incidentsSkill
- review-code-with-evidenceSkill
- route-ultracode-subagentsSkill
- verify-end-to-endSkill
- write-durable-documentationSkill
- write-tests-that-prove-behaviorSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Never push, enable a state that may integrate automatically, or merge unless both pass:
- Distinctive: line 21
Read repository and contribution instructions.
- Distinctive: line 25
Create a local commit only when the user asked for a commit or for delivery of the identified uncommitted work.
- Distinctive: line 42
Read back every destination and the target.
- Distinctive: line 59
When asking for an override, show the complete frozen descriptor, the missing controls, and residual risks.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Publish Verified GitHub Change
Own privileged Git and GitHub delivery, not implementation. Produce the candidate with the code-change and verification workflows; enter this skill only for the commit or remote operations actually requested.
Enforce two gates
Never push, enable a state that may integrate automatically, or merge unless both pass:
- Scope gate: the current request or a standing repository instruction explicitly authorizes that specific operation. "Implement", "fix", "build", and "refactor" authorize local work only. Authorization to push does not authorize a PR, queue enrollment, or merge; each is separate. Force pushes, history rewrites, deployments, releases, branch deletion, and issue closure need their own explicit scope.
- Verification gate: an independent reviewer approved the exact immutable candidate and the complete operation descriptor, or the user freshly confirmed that exact unverified operation after seeing its frozen descriptor, the missing review, and residual risks. An upfront "implement and push" passes only the scope gate.
Independent verification never creates remote authority; user authority never becomes independent verification. Tests, CI, linters, self-review, urgency, a clean diff, and reviewer unavailability are not overrides. Never deliver secrets, unrelated user work, an ambiguous change set, or known-broken acceptance behavior.
Freeze the candidate
- Read repository and contribution instructions. Resolve repository URL, remotes, default and target refs, current branch and upstream, open PRs on the destination, permissions, and worktrees.
- Inspect status, staged and untracked files, outgoing commits, ahead/behind, file modes, renames, submodules, generated files, and lockfiles. Stage explicit paths; never blanket-stage a contaminated tree. Preserve pre-existing work.
- Fetch remote state without pulling, merging, or rebasing through a dirty checkout. Confirm every included file belongs to one coherent delivery unit. Scan for credentials, private data, debug, and environment leakage without printing values.
- Run proportional focused, type, lint, build, regression, and runtime checks. Bind every result to its exact command, environment, commit, and tree; record baseline failures and checks that could not run. Material publication checks run in a clean checkout of the immutable candidate unless earlier evidence is demonstrably invariant.
- Create a local commit only when the user asked for a commit or for delivery of the identified uncommitted work. A request to push existing history does not authorize committing anything.
- Record the target ref and its exact base object, the merge base, outgoing range, head commit, and head tree. The target base must be an ancestor of the head and equal the merge base; otherwise update onto the exact base, rerun affected checks, and re-review. Use the raw-object Git settings in operation descriptors whenever the review is a gate.
Freeze the operation and obtain review
Build one operation-specific descriptor before review or override: every repository, destination ref, exact old and proposed object, base, method, topology, concurrency guard, consumer, and residual race. Use the matching variant in operation descriptors. A branch name, link, or summary is not a descriptor. Queue enrollment, auto-merge enablement, and each additional repository are separate operations.
Prefer a qualified human reviewer. Otherwise use a fresh context-isolated agent that did not implement the change and inspects the immutable candidate in a read-only checkout, following review-code-with-evidence. Give it the sanitized task contract with stable clause IDs, exact identifiers, the complete descriptor, aggregate diff and commits, and candidate-bound verification. Accept one verdict: APPROVED, CHANGES_REQUIRED (fix via the code-change workflow, new candidate, fresh review), or BLOCKED (resolve the gap or use the user-override path). Any change to the descriptor, base, range, head, tree, delivered byte, dependency, or generated artifact invalidates approval.
Execute the remote operation
Immediately before a direct push:
- Fetch and reread the target and every destination ref.
- Inventory every PR, auto-merge setting, or queue entry consuming a destination. Prefer a new unconsumed branch; otherwise require a provider-enforced barrier the publishing principal cannot bypass, or fresh user confirmation of the disclosed integration race.
- Recompute the descriptor and prove every field matches the approved one, including target-base ancestry.
- Push explicit source objects to fully qualified destination refs with a server-enforced expected-old lease per ref (
--force-with-lease=<ref>:<expected-old>, expected absence for creation),--no-follow-tags, no extra refspecs, no recursive submodule push, and--atomicfor multiple refs. If the server cannot enforce the lease or atomicity, stop. - Read back every destination and the target. Evidence for integration is stale if the target moved.
In normal mode every updated tip descends from its expected old object. Non-fast-forward rewrites, merge-queue enrollment, auto-merge, and provider merge or squash have additional descriptor and barrier rules in the reference; apply them before those operations.
Follow through
Open or update a PR only within scope, describing verified facts: outcome, scope, material decisions, exact checks and results, baseline failures and gaps, risks, rollout or rollback when relevant, and the reviewer type, scope, verdict, and snapshot. After every push inspect the provider-visible diff, head, merge base, reviews, unresolved threads, checks, queue state, and mergeability. Empty checks are missing automation, not success. Investigate CI failures from logs; distinguish regressions from baseline or infrastructure failures; never rerun blindly until green.
Merge only when explicitly authorized, the exact merge descriptor passed the verification gate, required checks and reviews pass on that candidate, actionable threads are resolved, and provider-race controls still hold. Read back the destination object, parents, tree, method, and PR state. Treat any mismatch as an incident.
Stop and ask when
- the request authorizes local work but not the remote operation being contemplated;
- independent review is unavailable or BLOCKED and no user override exists for this exact descriptor;
- a destination is consumed by a PR, queue, or auto-merge and no non-bypassable barrier exists;
- the target moved, the descriptor drifted, or the lease cannot be enforced.
When asking for an override, show the complete frozen descriptor, the missing controls, and residual risks. The confirmation removes only the independent-review prerequisite; label the result "user-authorized but not independently verified".
Done when
The report states local branch and commit, reviewed or confirmed snapshot and descriptor, commands and results, remote ref and read-back object, PR and check state, merge object and method when applicable, gaps, residual risks, and external actions not taken. Never say "pushed", "reviewed", "approved", "CI passed", or "merged" without exact read-back evidence.
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.

