Fix Push

Fix reported issues, validate, then commit and push using the Git playbooks. Use when the user types /fix-push.

blockmatic 9a7679c 1.0 KB Updated

File contents

Purpose and inputs

Invocation requests fix → validate → commit → push for the named issues. Preserve unrelated work. Never force-push, never --no-verify, never --trailer. This is not /exec-push (no PR) and not a merge or deploy.

Steps

  1. Address the reported errors, warnings, or feedback (lint, types, tests, reviews).
  2. Run pnpm qa in Basilic (or the consuming repo's documented full gate). Fix failures before publishing.
  3. Follow git-commit for intended paths only.
  4. Follow git-push. Do not use a bare git push that skips those rules.

Verification

  • The reported issues and the full gate were addressed.
  • Commit and push used the child playbooks.
  • Unrelated local changes remain intact.

Handoff

Report commit, branch, and push result. Do not open a PR unless the user asked /git-create-pr or /exec-push.

blockmatic/basilic-skills/tree/main/skills/workflow/fix-push commit 9a7679c456

Frequently asked questions

npx skillmds@latest add blockmatic/fix-push