git-push
無料Intelligently push the current git branch to its remote with safety checks. Use when invoked as `$git-push` or when the user asks to push committed work.
日本語の概要は準備中です。原文の説明を表示しています。
2,057 件 ・ 関連度順
概要と使いどころ
Intelligently push the current git branch to its remote with safety checks. Use when invoked as `$git-push` or when the user asks to push committed work.
日本語の概要は準備中です。原文の説明を表示しています。
Address GitHub PR review comments at line, file, and PR level by fetching, evaluating, fixing, committing, and resolving feedback. Use when invoked as `$pr-resolve-review-feedback` or when the user asks to resolve PR feedback.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate and fix failing CI. Takes a PR reference, one or more CI run/job URLs, or freeform text describing where the failures are, then enumerates failing workflows/jobs/steps, determines the root cause (often one shared cause behind several red checks), proposes a fix plan, applies code changes, commits, pushes, watches the new runs, and repeats until checks pass. Use when the user says "fix CI", "CI is red", "checks are failing", "the build is broken on my PR", "fix the failing jobs", or pastes a failing CI run URL. Do NOT use for authoring new workflows, or for read-only diagnosis with no fix intent — use gha-log-reader for that.
日本語の概要は準備中です。原文の説明を表示しています。
Turn an idea into a Conventional Docs Decision, then a Plan: classify the request, explore options and risks through dialogue, then commit a numbered Decision that review, prototypes, and acceptance move through. Use PROACTIVELY before any creative work — new features, new subsystems, interface or dependency changes, or any open-ended design question ("what are the options", "how should I approach", "should I use X or Y", "help me decide", "write a decision", "ADR").
日本語の概要は準備中です。原文の説明を表示しています。
Create and commit a durable handoff document that gives a fresh agent the context and prompt to continue the current planning or implementation work. Use only when explicitly invoked as `$handoff` or when the user explicitly requests a handoff.
日本語の概要は準備中です。原文の説明を表示しています。
Address GitHub PR review feedback at line, file, and PR level — fetch, evaluate, fix, commit, and resolve. Use when given a PR URL, a review-comment URL, or a PR-level comment URL. Triggers: GitHub discussion URLs, "fix this review comment", "address PR feedback", "resolve PR comments", PR URLs with #discussion_, #issuecomment-, or #pullrequestreview- fragments.
日本語の概要は準備中です。原文の説明を表示しています。
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
日本語の概要は準備中です。原文の説明を表示しています。
Initialize a Git repository with an initial commit
日本語の概要は準備中です。原文の説明を表示しています。
Initialize a Git repository with an initial commit
日本語の概要は準備中です。原文の説明を表示しています。
Set up and optimize repositories for AI coding agents. Creates minimal AGENTS.md, CLAUDE.md symlink, docs/REQUIREMENTS.md, docs/BUSINESS-RULES.md, feedback loops, and deterministic enforcement (Claude Code hooks, OpenCode plugins). Use when user wants to make a repo AI-friendly, set up AGENTS.md/CLAUDE.md, document requirements/business rules for AI, add pre-commit hooks for AI workflows, or optimize codebase structure for coding agents.
日本語の概要は準備中です。原文の説明を表示しています。
Implements one issue in its own git worktree (agent/issue-N): smallest correct change, self-check, commit, JSON report. Use when launched with AGENT_FLOW_ROLE=implementer or asked to implement a specific issue in a worktree.
日本語の概要は準備中です。原文の説明を表示しています。
Review gate for correctness, reuse, and simplification. Produces a structured verdict with actionable findings. Trigger on any PR before merge, or on any agent-generated code before it is committed.
日本語の概要は準備中です。原文の説明を表示しています。
Use when governing a worktree across its whole life — scope-lock declaration, merge-readiness status, scoped verification, and safe cleanup that refuses while unique unmerged commits exist.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need this project's coding standards (line length, quotes, import order, naming, commit format) — derive them from the REAL tooling config as a pointer + digest, never a guessed claim.
日本語の概要は準備中です。原文の説明を表示しています。
Use when claiming 'done', suggesting a commit, push, or PR — runs the evidence gate so completion claims come from fresh output in this message, not memory or earlier runs.
日本語の概要は準備中です。原文の説明を表示しています。
Use before committing to a heavy or irreversible plan — imagine it's 6 months later and this failed; enumerate why, score each mode, derive early-warning signals and preventive guardrails.
日本語の概要は準備中です。原文の説明を表示しています。
Use when surfacing and prioritising risk before commit — blast-radius framing, mitigations, residual-risk verdict — even if the user just says 'what could go wrong here?'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Git — branch naming, commit messages, PR creation, rebasing, or the code review process — even when the user says 'push this' or 'merge the branch' without naming Git.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user invokes a slash command like /create-pr, /commit, /fix-ci, or pastes command file content — routes to the right command with context inference and GitHub API patterns.
日本語の概要は準備中です。原文の説明を表示しています。
**REQUIRED** - Always activate FIRST on any git/VCS operations (commit, status, branch, push, etc.), especially when HEAD is detached. If `.jj/` exists -> this is a Jujutsu (jj) repo - raw git commands can corrupt data. Essential git safety instructions inside. DO NOT IGNORE.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when reviewing rationale and change quality for plans, PBIs, commits, diffs, docs, specs, reports, or explicit artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
[Git] Use when generating developer KPI, performance, contribution value, story point, man-day, or code-quality reports from local git commit history.
日本語の概要は準備中です。原文の説明を表示しています。
[Quality] Use when you need to research and configure code quality tooling for any tech stack — linters, formatters, static analysis, pre-commit hooks, and CI gates.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare monthly timesheet entries from Git commits.
日本語の概要は準備中です。原文の説明を表示しています。