commit-and-pr

Étoiles15

Forks6

Mis à jour3 août 2026 à 05:41

Run Hazma's preflight gate, create or validate a Codex branch, commit intentionally with a valid Conventional Commit header, push, and open or update a pull request. Use when a user asks to commit, ship, or open a PR for current work.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

LoganAMorrison

LoganAMorrison/Hazma

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	commit-and-pr
description	Run Hazma's preflight gate, create or validate a Codex branch, commit intentionally with a valid Conventional Commit header, push, and open or update a pull request. Use when a user asks to commit, ship, or open a PR for current work.

Commit and open a pull request

Ship the current worktree without bypassing Hazma's gates. This is the commit authority for standalone work; a pipeline-owned branch keeps its existing branch and PR instead.

Read docs/PR_GUIDELINES.md, inspect git status --short, the full diff, and recent commit style. Stop if there are no intended changes.
Confirm numerical-impact evidence for any public code path, and confirm a closing project carries its required VERSION and CHANGELOG.md updates.
Work only on a feature branch. If a new branch is needed, create codex/<project>/<task> for project work or codex/<description> for ad-hoc work; never commit to master.
Rebuild first when Cython sources changed, then run:
```
scripts/agents/preflight.sh --paths "<touched paths>" \
  --tests "<test targets>" [--md "<changed markdown>"] [--closing]
```
Treat a non-zero result or WARN gate as a blocker. Read the literal pytest summary and use the sequential critical path in docs/agents/preflight.md.
Stage only intended source, test, and documentation files. Do not stage build outputs, credentials, scratch files, or generated C/C++.
Compose and validate the commit/PR header before committing:
```
scripts/agents/check_pr_title.py "type(scope): subject"
```
Immediately before the commit, verify the intended non-master branch and worktree. Commit with an explanatory body when it helps.
Push without force, verify HEAD equals origin/<branch>, and create or update a PR against master. Use the validated header as the title. The PR body must contain ## Summary and ## Test plan, plus ## Project for project work. Reconcile all prose claims with the current diff and actual command output; state every published numerical change explicitly.
Watch CI to a bounded conclusion. If it fails, report the failing check or fix it through the full gate again; never report a red PR as complete.

End with:

STATUS: Pushed | PR opened | Committed-only | Failed
BRANCH: <branch>
COMMIT_SHA: <short sha>
PR_URL: <url or n/a>
TITLE: <validated title>

Plus depuis ce dépôt

même dépôt

begin-phase

LoganAMorrison/Hazma

Prepare a guarded, ready-to-paste kickoff prompt for the next eligible phase of a phased project, verifying strict prerequisite closeout first and refusing blocked or ambiguous phase starts.

2026-08-0315

begin-phase

LoganAMorrison/Hazma

Safely determine whether a phased Hazma project can begin its next or a requested phase, then produce a guarded Codex kickoff prompt. Use when a user asks which phase is ready, asks to begin a phase, or needs a phase handoff; this skill does not implement the task.

2026-08-0315

execute-single-task

LoganAMorrison/Hazma

Implement exactly one numbered task from a Hazma project plan, including task-note updates, numerical-impact measurement, documentation consistency, and the preflight gate. Use when a user asks to take a project task or the next project task; stop before committing unless the caller expressly owns the commit.

2026-08-0315

review-cycle

LoganAMorrison/Hazma

Orchestrate a bounded, multi-agent Codex review loop for a pushed Hazma pull request: select independent reviewer lenses, collect reviews in parallel, apply and push justified fixes, verify them, post durable round summaries, and stop at convergence, escalation, or the iteration cap.

2026-08-0315

review-plan

LoganAMorrison/Hazma

Perform a read-only, findings-first review of a Hazma project PLAN before implementation, covering feasibility, numerical correctness, architecture, Python conventions, and testability. Use when a user asks whether a project plan is ready or asks to review projects/<slug>/PLAN.md.

2026-08-0315

review-pr

LoganAMorrison/Hazma

Review a Hazma pull request against its project task or ad-hoc scope using one focused lens: generalist, completeness, logic, document consistency, or numerics. Use when a user asks for a PR review or when a Codex review cycle assigns a single reviewer lens.

2026-08-0315

name	commit-and-pr
description	Run Hazma's preflight gate, create or validate a Codex branch, commit intentionally with a valid Conventional Commit header, push, and open or update a pull request. Use when a user asks to commit, ship, or open a PR for current work.

Commit and open a pull request

Ship the current worktree without bypassing Hazma's gates. This is the commit authority for standalone work; a pipeline-owned branch keeps its existing branch and PR instead.

Read docs/PR_GUIDELINES.md, inspect git status --short, the full diff, and recent commit style. Stop if there are no intended changes.
Confirm numerical-impact evidence for any public code path, and confirm a closing project carries its required VERSION and CHANGELOG.md updates.
Work only on a feature branch. If a new branch is needed, create codex/<project>/<task> for project work or codex/<description> for ad-hoc work; never commit to master.
Rebuild first when Cython sources changed, then run:
```
scripts/agents/preflight.sh --paths "<touched paths>" \
  --tests "<test targets>" [--md "<changed markdown>"] [--closing]
```
Treat a non-zero result or WARN gate as a blocker. Read the literal pytest summary and use the sequential critical path in docs/agents/preflight.md.
Stage only intended source, test, and documentation files. Do not stage build outputs, credentials, scratch files, or generated C/C++.
Compose and validate the commit/PR header before committing:
```
scripts/agents/check_pr_title.py "type(scope): subject"
```
Immediately before the commit, verify the intended non-master branch and worktree. Commit with an explanatory body when it helps.
Push without force, verify HEAD equals origin/<branch>, and create or update a PR against master. Use the validated header as the title. The PR body must contain ## Summary and ## Test plan, plus ## Project for project work. Reconcile all prose claims with the current diff and actual command output; state every published numerical change explicitly.
Watch CI to a bounded conclusion. If it fails, report the failing check or fix it through the full gate again; never report a red PR as complete.

End with:

STATUS: Pushed | PR opened | Committed-only | Failed
BRANCH: <branch>
COMMIT_SHA: <short sha>
PR_URL: <url or n/a>
TITLE: <validated title>