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

始める

commit-framework

スター5

フォーク0

更新日2026年6月28日 23:13

Unified identify-verify-stage-commit workflow for skill-driven commits.

インストール

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

Manusで実行

ソース

joeharris76

joeharris76/BenchBox

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

ダウンロード

Manusで実行

Commit Framework

Use only when a calling skill authorizes a write-shaped commit.

Inputs

Parameter	Meaning
`file_scope`	Exact file discovery rule
`prefix`	Conventional type: `feat`, `fix`, `refactor`, `docs`, `test`, `chore`
`verify_cmd`	Required pre-commit verification

Steps

Discover files from file_scope; no files -> "No files to commit."
Inspect git status --porcelain {files}, git diff {files}, and recent log.
Run verification; fix failures or stop without committing.
Stage and commit explicit files in one shell command.
Push after successful commit; if no upstream, push with -u origin {branch}.

Rules

Never git add -A.
Commit only authorized/session-modified files.
Use Conventional Commits.
Do not commit if verification fails or scope is ambiguous.
Push and other deterministic close-out gates (PR-open equivalent, CI status) may be delegated to a low-effort subagent for run-and-report only; the caller keeps failure analysis and fixes. See SHARED/verify-framework/SKILL.md.

このリポジトリの他の Skills

同じリポジトリ

review-protocol

joeharris76/BenchBox

Shared protocol for review-shaped actions, authorization scope, defect routing, L2 audit handling, and local-only capture.

2026-07-225

benchbox-workflow

joeharris76/BenchBox

Use when the user asks to "test TPC-H", "check compliance", "review architecture", "run quality checks", "check binaries", "test dialect translation", "compare implementations", "run live platform tests", or "plan and execute" a benchmark feature.

2026-07-215

code

joeharris76/BenchBox

Use for "commit code", "review code", "fix lint/type error", "improve performance", "compare code", "shrink code", "generate spec from code", "investigate code", "debug an error", "triage a bug", "iterate to green", or "create handoff prompt".

2026-07-215

docs

joeharris76/BenchBox

Use when the user asks to "create documentation", "build docs", "review docs", "compare documents", "compress docs", "adversarial review docs", or "commit docs".

2026-07-215

skill-sync

joeharris76/BenchBox

Use when the user asks to "sync skills", "set up skill-sync", "check skill status", "validate skills", "preview skill changes", "diagnose skills", "pin a skill", "unpin a skill", "prune skills", or "promote skill changes".

2026-07-215

test

joeharris76/BenchBox

Use when the user asks to "run tests", "create tests", "fix failing test", "add test coverage", "fix slow tests", or "commit test changes".

2026-07-215

name	commit-framework
description	Unified identify-verify-stage-commit workflow for skill-driven commits.

Commit Framework

Use only when a calling skill authorizes a write-shaped commit.

Inputs

Parameter	Meaning
`file_scope`	Exact file discovery rule
`prefix`	Conventional type: `feat`, `fix`, `refactor`, `docs`, `test`, `chore`
`verify_cmd`	Required pre-commit verification

Steps

Discover files from file_scope; no files -> "No files to commit."
Inspect git status --porcelain {files}, git diff {files}, and recent log.
Run verification; fix failures or stop without committing.
Stage and commit explicit files in one shell command.
Push after successful commit; if no upstream, push with -u origin {branch}.

Rules

Never git add -A.
Commit only authorized/session-modified files.
Use Conventional Commits.
Do not commit if verification fails or scope is ambiguous.
Push and other deterministic close-out gates (PR-open equivalent, CI status) may be delegated to a low-effort subagent for run-and-report only; the caller keeps failure analysis and fixes. See SHARED/verify-framework/SKILL.md.