「commits」の検索結果

Git history'den otomatik changelog, semantic versioning, release notes, conventional commits

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

Create git commits with user approval and no Claude attribution

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

Manage Git branching strategies, commit conventions, and collaboration workflows. Use when choosing between trunk-based development, GitHub Flow, or GitFlow, implementing conventional commits for automated versioning, setting up Git hooks for quality gates, or organizing monorepos with clear ownership.

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

Precision-first adversarial bug hunting for runtime, logic, data, concurrency, and security defects. Uses deterministic risk triage, evidence-bounded retrieval, Hunter/Skeptic/Referee review, optional hybrid verification, and explicit immutable Fixer scope. Scan-only and single-pass by default; complete-coverage loops, edits, autonomous fixes, and commits each require explicit intent. Use for code review, security audits, regression hunting, PR review, and evidence-backed remediation planning in skills-capable coding agents.

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

Stage and commit changes using conventional commits format

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

Comprehensive documentation specialist covering API documentation, technical writing, design documentation, migration guides, and changelog generation. Use when creating OpenAPI/Swagger specs, generating SDKs, writing user guides, creating README files, documenting architecture, writing design specs, creating ADRs, writing migration guides, or generating changelogs from git commits. Handles versioning, examples, developer experience, and user-facing documentation.

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

Best practices for creating GitHub pull requests including conventional commits, PR formatting, and multi-language support (en/ja). Use when creating PRs, writing PR descriptions, or formatting commit messages.

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

Implements code changes and creates commits. Triggered when: implementation tasks, code changes, feature additions, bug fixes.

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

Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".

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

Shared commit message rules and technical constraints for skills that write commits. Not typically invoked directly.

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

Use when creating or updating pull requests with comprehensive descriptions and meaningful commits - streamlines PR workflow with branch management and commit best practices

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

Use when the user explicitly asks to commit and push the current repository changes. Suitable for analyzing current changes, generating an English commit message that follows the repo's conventions, and completing the push. Not suitable for status-only checks, local-only commits, push-disallowed contexts, or any case where the user has not explicitly asked to write to the remote.

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

Summarize authored commits over a user-specified time period into a concise update

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

Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work

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

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

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

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then guards against regression. Use when asked to make a route's navigation instant (its static shell commits immediately), fix a route whose static shell isn't prerendered/served/prefetched, grow a route's static shell or fix its slow first paint, diagnose which Suspense boundary keeps a route out of its static shell, or write the instant() e2e guard for one. Requires Next.js 16.3+ with cacheComponents; directs an upgrade if older.

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

Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".

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

Cascades a rebase through an entire PR stack after a base PR merges or upstream changes. Use when a stack needs to incorporate new base branch commits.

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

Generates conventional commit messages from staged changes. Use when committing and needing a well-formatted message. Do not use for full PR prep; use pr-prep.

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

Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct.

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

Pushes all branches in a stack and opens or updates one dependent PR per slice. Use after stack-create to publish the stack or after adding commits to a slice.

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

Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.

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

Создаёт git-коммит в формате Conventional Commits по текущим изменениям. Используй, когда просят закоммитить или сделать коммит.

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

Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.

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