Results for “push”

非対話セッション（claude-code の remote-control / CI など TTY が無く SSH 鍵パスフレーズを入力できない状況）で git push を通すスキル。remote が SSH URL で `ssh -o BatchMode=yes` による非対話 SSH 認証が実際に通る（agent の鍵・パスフレーズ無しのディスク鍵・macOS キーチェーン鍵のいずれでも可）なら素の SSH push を実行し、非対話 SSH 認証が通らず `git push` が `Permission denied (publickey)` で失敗する場合は、push を HTTPS + gh トークン（credential.helper='!gh auth git-credential'）経由へ自動フォールバックして標準入力なしで実行する。「push して」「リモートに反映して」と頼まれたが SSH 認証が使えない、push が publickey で弾かれた、remote-control から push したい、といった場面で使う。`/gh-push` で明示起動も可。GitHub(gh) 前提。

The English summary is being prepared. Showing the original description.

変更を git-cz 形式でコミットする。リポジトリの直コミット可否の判定手順と、push 後の CI・conflict の確認を含む。/commit 実行時、「コミットして」「pushして」等の依頼時に使用。--push 引数または「pushして」の依頼で push も行う。境界: PR 作成は create-draft-pr、PR コメントへの対応コミットは pr-comment から呼ばれる。

The English summary is being prepared. Showing the original description.

Set up Claude Code hooks that block specified Git commands before they run, including push and destructive cleanup operations. Choose project or global installation, adjust the blocked commands, and test that the hook rejects a sample command.

• Blocking git push from Claude Code
• Preventing commands that discard local changes
• Installing Git guardrails across projects

Collect PR review feedback, check each finding against code and documentation, and fix valid issues. Run project checks, commit and push changes, then reply to review threads and resolve fixed findings or false positives.

• Deduplicating feedback from multiple reviewers
• Checking review findings against current code
• Testing and pushing fixes for valid findings

Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.

The English summary is being prepared. Showing the original description.

Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.

The English summary is being prepared. Showing the original description.

Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.

The English summary is being prepared. Showing the original description.

Run repository commands, inspect Git state, investigate CI or build failures, and verify focused fixes. Report the commands and results as evidence, clearly distinguishing local changes, local verification, commits, and pushes.

• Inspecting repository and branch state
• Investigating CI or build failures
• Making and verifying a focused fix

Record pushup and squat repetitions in Peon Trainer by telling the agent the exercise and count. It reports the updated total, plays a trainer voice line, and can check your progress after logging.

• Logging pushups after a set
• Recording completed squats
• Checking progress after logging

Save code changes on a new Git branch, select files to commit, and push them to the remote repository. Prepare a descriptive commit message and optionally create a pull request with a summary and test plan.

• Saving changes on a new branch
• Writing a commit message that explains the reason for a change
• Pushing changes and creating a pull request

Set up Claude Code hooks that block Git commands such as push, hard reset, and forced deletion before execution. Choose project-wide or global settings, customize the blocked commands, and verify that the hook rejects a test command.

• Block Git pushes from Claude Code
• Prevent commands that discard changes or delete branches
• Apply Git restrictions to one project or all projects

Prepare a branch for a pull request by running local tests, checking types for Node projects, pushing commits, and showing the CI pipeline link. Failed checks stop the workflow before the push.

• Running tests before opening a pull request
• Checking Node types before pushing commits
• Getting the CI link after a push

Publish saved skill and global AGENTS.md changes to a private repository, then check the automated public mirror. The workflow isolates intended edits, preserves unrelated work, and verifies the actual published content.

• Publishing changes to existing skills
• Syncing global AGENTS.md instructions
• Publishing while unrelated local edits are present

Expert guide for Monte Carlo's push ingestion model. Use this skill whenever a customer or engineer mentions: pushing data to Monte Carlo, the IngestionService, pycarlo push APIs, build me a collection script, push metadata/lineage/query logs, invocation_id tracing, custom lineage nodes or edges, deleting push tables, or any question about why pushed data is not showing up. Also trigger when they ask to generate code that collects metadata, table schema, row counts, freshness, lineage, or query history from any data warehouse or data source and sends it to Monte Carlo. If the user mentions any warehouse, database, or data platform alongside any Monte Carlo topic, this skill is almost certainly relevant.

The English summary is being prepared. Showing the original description.

Publish a new Canvas Notebook release. Use this skill whenever the user asks to bump a version, prepare release notes, update CHANGELOG.md, create or push a git tag, publish a GitHub Release, deploy, or automate the release workflow. This skill covers the full release sequence for this repository: inspect commits/tags, push completed product-code commits first when authorized, confirm the pushed code has built on GitHub, choose the next calendar version, update package and CLI versions, update the changelog, run the required local build, commit, push the release commit, wait for the remote Build and Push worker on the pushed branch, tag, push the tag, and publish the release.

The English summary is being prepared. Showing the original description.

Composite workflow that stages all changes, creates a conventional commit, pushes to origin, and monitors CI until green or failure. Use when you want to commit and push in one step with CI monitoring. Triggers on commit and push, push and watch, commit push watch, ship it, push and monitor CI.

The English summary is being prepared. Showing the original description.

Create atomic git commits with terse Conventional Commits messages, then push to remote. Subject ≤50 chars, body only when "why" isn't obvious. Never force pushes. Use when the user says "commit and push", "commit & push", "/commit-push", or asks to stage, commit, and push in one flow.

The English summary is being prepared. Showing the original description.

Update the caniuse-lite version override in Remotion to the latest release on npm. The workflow checks the branch and working tree, updates package.json, reinstalls dependencies with Bun, then commits and pushes the change.

• Update caniuse-lite to the latest npm release
• Refresh the version override in package.json
• Reinstall dependencies after the version update

Organize changes into focused branches and commits, write consistent commit messages and pull requests, and run relevant checks before pushing. It also handles dependent pull requests, CI follow-up, and updates that preserve review history.

• Committing changes in logical units
• Writing pull request titles and descriptions
• Splitting dependent work across pull requests

Stage files, create a commit, and push in one step. Use when the user asks to "stage commit and push", "add commit and push", "commit and push", or "commit and push my changes".

The English summary is being prepared. Showing the original description.

A gate before git push / deploy — assembled from your own tools (secret-grep + slop-scan + code-review + build/compile + optional worktree isolation), so AI junk (slop / bugs / secrets / uncompiled code) never reaches a remote or a production server. Turns "I hope it's clean" into a verifiable criterion. Branches: web/OSS (git push/PR) vs deploy-to-server service. Triggers — "check before push", "clean push", "gate before push", "finalize before commit", "run before deploy".

The English summary is being prepared. Showing the original description.

親イシュー配下のサブイシュー（孫以下の全子孫を含む）を依存順を保ちつつ worktree で並列に自動実装・push 前 review・PR 作成・CI 監視・マージ可能状態化まで一括自動化。 「イシューツリーを並列実装」「配下のサブイシューをまとめて実装」「ツリー全体を並列で実装して」「イシュー階層を自動開発」で使用。 per-issue 計画立案（Plan: セッション継承モデル）→実装（Implement: sonnet）の分業。push 前 review（Review 通過後にのみ push・PR 作成して CI を 1 回だけ起動）。 外部チェック構成は args の externalChecks で明示（{"app", "context"} の組で宣言。[] で「なし」を確定して不要待機なし・未指定なら自動マージ停止・slug のみの旧形式は自動マージ fail-closed）。 自動 squash merge は autoMerge: true + externalChecks 明示（全 App の信頼済み context 宣言込み）の opt-in で実行（merge-exec の自己取得再検証 + サーバー側 branch protection 実測が前提。既定 false はマージ可能状態で停止し人間がマージ。サーバー側 workflow サンプル（upstream の docs/implement-issue-tree/auto-merge-sample.yml 参照）+ branch protection への委譲も可）。並列度（parallel）と依存（dependsOn）で実行順を制御。 Phase 単位で厳密に直列化したい場合は phaseGate: true（opt-in。ルート直下の子〔Phase 親〕を sub-issues リスト順に直列化し、前 Phase の全子孫が merged/closed になるまで次 Phase 配下に着手しない。既定 false は現行の post-order 優先度のみ）。 着手できる件数・blocked になる件数を事前に知りたい場合は dryRun: true（何も書かずに見積りだけ返す）。 単一イシューの実装は implement-issue、PR レビューは implement-review-pr を参照。

The English summary is being prepared. Showing the original description.

Calculates added and deleted lines for a pull request and maintains a three-line summary for implementation, tests, and other files. Preserves existing description text and checks the published counts against the current diff.

• Add change counts to a new pull request
• Refresh counts after the final push
• Classify tests and generated files

Push the current Git branch and get a link to its GitLab CI or GitHub Actions runs. The workflow checks for uncommitted changes and blocks direct pushes to main, master, and production before proceeding.

• Pushing a committed feature branch
• Finding the GitLab CI tracking link after a push
• Finding GitHub Actions runs for the current branch