本文へ移動
cccskills
無料GitHub で公開

push

Publish local Git commits on a named branch without losing local or remote work. Always use this skill for an actual Git branch publication, including requests to push, publish, upload, or put the current or detached checkout on origin or another Git remote. Use it for detached-HEAD publication and post-rebase lease-protected updates; it pushes existing commits only and does not commit dirty changes, create a PR, or merge.

日本語の概要は準備中です。原文の説明を表示しています。

toy-crane/claude-code-playbook-templateスター 77(GitHub 77 + cccskills 0)

実行スコア 未検証

インストール方法を見る

含まれるファイル(6)

  • SKILL.md1.3 KB
  • agents/openai.yaml211 B
  • evals/control-trigger-evals.json470 B
  • evals/evals.json2.9 KB
  • evals/heldout-trigger-evals.json730 B
  • evals/trigger-evals.json1.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Push branch

Publish the current branch's commits while leaving uncommitted changes local. Report dirty changes as not included rather than turning a push request into a commit request.

Publish a named working branch. When the checkout is detached, derive a concise branch name from the change. Treat a protected default branch as requiring explicit authorization rather than a routine push target.

Reconcile the current remote branch before updating it so another contributor's work is preserved. When an intentional rebase changed already-published history, use a lease-protected update only against the remote state just observed; never overwrite an unexpectedly changed remote.

Finish when the remote branch points at the intended local commit, upstream tracking is usable for later work, and the user knows the branch and remote result. Keep every uncommitted or unrelated change untouched.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

Audit and establish current agent context for the technologies that define a project's stack. Use when setting up a project for agent work, after selecting or adding a framework, library, developer tool, or hosted service, or when entering an existing project whose agent context has not been audited.

日本語の概要は準備中です。原文の説明を表示しています。

toy-crane/claude-code-playbook-template772026年10月21日 更新

Revise active `docs/specs/SLUG/` specs so they match what has shipped since they were written. Use when earlier work has landed and queued specs may now rest on stale assumptions, acceptance criteria, constraints, terms, or prototypes, or when implementation reports a spec as stale before changing source. Takes one or more spec folders, or every folder under `docs/specs/` when none is named. Do not use to shape a new spec from a problem and direction, which belongs to `shape-idea`, or to reconcile durable project context and retire shipped folders, which belongs to `maintain-project-context`.

日本語の概要は準備中です。原文の説明を表示しています。

toy-crane/claude-code-playbook-template772026年10月21日 更新

Build a complete dummy-data HTML prototype or a temporary comparison of up to three alternatives for a specific user situation. Use to settle a screen-based product before implementation or resolve a visual or interaction decision during shaping or prototype review. Do not use for production implementation or CLI, terminal, or voice interfaces.

日本語の概要は準備中です。原文の説明を表示しています。

toy-crane/claude-code-playbook-template772026年10月21日 更新

commit

無料

Create Git commits for the current request's in-scope changes as logical Conventional Commits. Always use this skill for an actual Git commit operation, including requests to commit or amend changes, save work in repository history, stage and record selected files, or group staged or unstaged changes into commits. Use it even when the request describes recording changes without saying "commit"; it performs the commit rather than only suggesting a message, and it does not push.

日本語の概要は準備中です。原文の説明を表示しています。

toy-crane/claude-code-playbook-template772026年10月21日 更新

Interview the user to define or revise the app's overall product direction, then preserve the confirmed meaning in root PRODUCT.md. Always use for a new app direction or any app-wide change to users, usage situations, problem, promised change, core loop, durable boundaries, experience principles, success signals, assumptions, or unknowns, even when PRODUCT.md is not named. Start from an existing definition or a rough app direction. Do not use for blank-page idea discovery, architecture, or shaping or specifying one feature or work unit.

日本語の概要は準備中です。原文の説明を表示しています。

toy-crane/claude-code-playbook-template772026年10月21日 更新

Render an explanation as a diagram, comparison, trace with real values, or annotated code. Use when the user asks to have a concept, decision, flow, or code explained, or says they do not follow.

日本語の概要は準備中です。原文の説明を表示しています。

toy-crane/claude-code-playbook-template772026年10月21日 更新

toy-crane のスキルをすべて見る

このスキルの問題を報告する