zendev-lab/ulota / .agents/skills/spark-pre-push-checks
spark-pre-push-checks
VerifiedUse when a Spark branch or pull request needs final diff hygiene, validation selection, commit scope, remote topology, and readiness checked before publication.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.2 KB |
SKILL.md
View on GitHub---
name: spark-pre-push-checks
description: Use when a Spark branch or pull request needs final diff hygiene, validation selection, commit scope, remote topology, and readiness checked before publication.
---
# Spark pre-push checks
Treat repository and remote state as evidence. The upstream Session retains publication authority.
## Procedure
1. Read `CONTRIBUTING.md`, the validation matrix, PR template, and applicable subtree instructions.
2. Inspect status, staged and unstaged diffs, commit range, generated output, secrets, runtime state, and unrelated edits.
3. Map changed owners to focused tests, static checks, documentation checks, and compatibility gates. Run missing non-publishing checks when authorized.
4. Compare every acceptance criterion with concrete code or command evidence.
5. For an existing PR or stack, read back exact head/base SHAs, topology, mergeability, and current checks. Mark pending checks as pending.
Never push, force-push, create, ready, merge, or close a PR. Never claim a check passed from an old SHA. Reject when intended commit scope is ambiguous or required evidence is absent.
Return `diffScope`, `commands`, `acceptanceEvidence`, `remoteState`, `pending`, `verdict`, and `blockingReasons`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |