ワンクリックでManusで任意のスキルを実行

reword-head-commit

スター0

フォーク0

更新日2026年4月9日 12:12

Rewrite only the current HEAD commit message to the active repository's commit-message rules. Use when Codex needs a fast amend-based path for one clean HEAD commit with explicit repo guidance and no packet or replay audit requirements.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

FennexFox

FennexFox/packetflow_foundry

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Reword Head Commit

Use this skill for the narrow express path that validates one replacement message and amends HEAD directly.

Use When

the target is exactly HEAD
the worktree is clean and repo commit-message rules are explicit
packet generation or replay-style history rewriting would be unnecessary overhead

Execution Roots

<skill-dir>: directory containing this SKILL.md
<python-bin>: concrete interpreter path; on Windows prefer a non-WindowsApps Python and reuse the same resolved interpreter path for the whole run
<artifact-root>: <repo-root>/.codex/tmp/packet-workflow/reword-head-commit/<run-id>/

Entry

Prepare the full replacement message.

Pass it directly with --message, or store it under <repo-root>/.codex/tmp/packet-workflow/reword-head-commit/ and use --message-file.

Run the express driver.

Run <python-bin> -B <skill-dir>/scripts/reword_head_commit.py --repo <repo-root> --message <full-message>.
Or run <python-bin> -B <skill-dir>/scripts/reword_head_commit.py --repo <repo-root> --message-file <message-path>.
Add --apply only after confirmation. Without --apply, the driver stops after validation and writes a dry-run apply summary.

Use the emitted validation/apply artifacts to report the outcome; keep any later push decision outside this skill.

Continue Only If

repo commit-message rules are explicit enough for the express path
the worktree is clean, HEAD is attached, no git operation is active, and HEAD is neither a merge commit nor the root commit
the amend stays local and no push is attempted from this workflow
the express path keeps using the shared reword validation contract instead of inventing a separate rule parser

Stop When

repo rules are derived or fallback-only
the worktree is dirty or another git operation is active
HEAD is detached, a merge commit, or the root commit
the replacement message fails validation

Final Response

say whether validation blocked the run or the amend succeeded
include the new head when the amend ran
name the blocker precisely when the run stops
mention whether a later force-push is likely

References

references/reword-head-commit-contract.md
references/amend-safety.md
references/core-contract.md
references/reword-head-commit-evaluation-contract.md
<python-bin> -B <skill-dir>/scripts/smoke_reword_head_commit.py

このリポジトリの他の Skills

同じリポジトリ

draft-release-copy

FennexFox/packetflow_foundry

Draft and validate reusable release-copy updates by collecting release evidence, preparing publish configuration and README updates, and normalizing release-issue create or edit actions. Use when Codex must turn tracked repo state plus release evidence into guarded release-copy edits without encoding project-specific release policy in the retained kernel.

2026-04-100

gh-address-review-threads

FennexFox/packetflow_foundry

Inspect unresolved GitHub PR review threads on the open pull request for the current branch, decide whether to accept, reject, defer, or defer outdated threads, post acknowledgement and completion replies with gh CLI, apply accepted fixes, and resolve completed threads. Use when Codex needs to read open PR review threads, summarize the planned direction or rejection, perform the work, then post a completion reply and resolve the finished threads.

2026-04-100

gh-create-pr

FennexFox/packetflow_foundry

Create a GitHub pull request from an already-pushed branch by collecting repo and PR-template context, drafting a repo-compliant title/body, validating duplicate-PR and stale-snapshot gates, and creating the PR with gh CLI only after the normalized create request passes validation. Use when Codex must open a new PR instead of rewriting an existing one.

2026-04-100

gh-fix-pr-writeup

FennexFox/packetflow_foundry

Verify and repair a GitHub pull request title and body when the user gives a PR number or asks to audit, rewrite, or fix PR text. Use when Codex must compare a PR's current writeup against repository PR instructions/templates and the actual code changes, then update it with gh CLI if the title/body are missing, truncated, generic, misleading, or unsupported by the diff.

2026-04-100

git-split-and-commit

FennexFox/packetflow_foundry

Review the active repository's current working tree, split local changes into logical commits, draft repo-compliant commit messages, and commit automatically when confidence is high. Use when Codex needs to inspect staged, unstaged, and untracked non-ignored changes, decide whether they belong in one or more commits, and apply the commits safely with packetized evidence and targeted validation.

2026-04-100

public-docs-sync

FennexFox/packetflow_foundry

Audit and synchronize public repository docs against tracked runtime metadata, selected GitHub evidence, and validator-normalized deterministic edits. Use when Codex must detect public-doc drift, propose scoped fixes, and update marker state without embedding repo-specific governance policy in the retained kernel.

2026-04-100

name	reword-head-commit
description	Rewrite only the current HEAD commit message to the active repository's commit-message rules. Use when Codex needs a fast amend-based path for one clean HEAD commit with explicit repo guidance and no packet or replay audit requirements.

Reword Head Commit

Use this skill for the narrow express path that validates one replacement message and amends HEAD directly.

Use When

the target is exactly HEAD
the worktree is clean and repo commit-message rules are explicit
packet generation or replay-style history rewriting would be unnecessary overhead

Execution Roots

<skill-dir>: directory containing this SKILL.md
<python-bin>: concrete interpreter path; on Windows prefer a non-WindowsApps Python and reuse the same resolved interpreter path for the whole run
<artifact-root>: <repo-root>/.codex/tmp/packet-workflow/reword-head-commit/<run-id>/

Entry

Prepare the full replacement message.

Pass it directly with --message, or store it under <repo-root>/.codex/tmp/packet-workflow/reword-head-commit/ and use --message-file.

Run the express driver.

Run <python-bin> -B <skill-dir>/scripts/reword_head_commit.py --repo <repo-root> --message <full-message>.
Or run <python-bin> -B <skill-dir>/scripts/reword_head_commit.py --repo <repo-root> --message-file <message-path>.
Add --apply only after confirmation. Without --apply, the driver stops after validation and writes a dry-run apply summary.

Use the emitted validation/apply artifacts to report the outcome; keep any later push decision outside this skill.

Continue Only If

repo commit-message rules are explicit enough for the express path
the worktree is clean, HEAD is attached, no git operation is active, and HEAD is neither a merge commit nor the root commit
the amend stays local and no push is attempted from this workflow
the express path keeps using the shared reword validation contract instead of inventing a separate rule parser

Stop When

repo rules are derived or fallback-only
the worktree is dirty or another git operation is active
HEAD is detached, a merge commit, or the root commit
the replacement message fails validation

Final Response

say whether validation blocked the run or the amend succeeded
include the new head when the amend ran
name the blocker precisely when the run stops
mention whether a later force-push is likely

References

references/reword-head-commit-contract.md
references/amend-safety.md
references/core-contract.md
references/reword-head-commit-evaluation-contract.md
<python-bin> -B <skill-dir>/scripts/smoke_reword_head_commit.py