「commits」の検索結果

Fork divergence monitor - tracks where the fleet's active forks diverge in CODE (unique commits, new/modified skills) and CONFIG (enable/var/model/schedule vs upstream), gated on real change.

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

Turn a set of commits or a diff into a clean, user-facing changelog entry. Use before a release or PR description.

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

Generate changelogs from git commits. Use when user says "generate changelog", "update changelog", "what changed since last release", or before preparing a new release.

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

Use when the user wants to roll back GSD commits: the last N, a whole phase, or one plan. Reverts through the phase manifest with dependency checks and a confirmation gate before anything is undone.

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

Use when the user wants a GitHub PR (URL, owner/repo#N, or 'this PR') made into a code-change explainer video from its diff and commits: changelog, feature reveal, fix, or refactor. Not a product promo; unclear goes to /hyperframes.

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

Use after /gsd-audit-uat when the user wants the findings fixed, not just listed. Classifies each issue as auto-fixable or manual and fixes the auto-fixable ones with test verification and atomic commits; --severity sets the floor.

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

Use when the user wants to pause work mid-phase or hand it off to a new session. Writes .continue-here.md with position, completed and remaining work, decisions and blockers, commits it as WIP, and prints resume instructions.

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

Use when opening a pull request and the diff is cluttered with .planning/ commits. Creates a clean branch filtered of GSD planning artifacts so reviewers see only code changes.

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

Use when the user wants a small, ad-hoc change handled with GSD guarantees (atomic commits, STATE.md) but without the full pipeline. Tasks land in .planning/quick/; --full, --discuss, --research, --validate add the skipped agents back.

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

Use after gsd-code-review has written REVIEW.md, when you want its Critical and Warning findings fixed. Spawns the fixer agent, commits each fix atomically and writes REVIEW-FIX.md (--all, --auto to iterate).

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

Use when a planned but unstarted phase should come off the roadmap. Removes the phase, renumbers the phases after it into a clean sequence, and commits the change as the historical record.

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

Use when finished work needs to reach a coco-managed repository (coco-research/coco or similar) — verifies branch state, commits, pushes through the corporate DLP guard only when actually needed, opens a PR against main, waits for CI, and reports the result. Never merges, never pushes to main directly.

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

Start a safe, governed autonomous loop from a plain-language goal. Use when the user says /coco-loop, "run an autonomous loop", "keep my build green for N hours", "work on X autonomously for a while", or wants a bounded self-improving loop that proposes fixes and never commits on its own. Turns a vague goal into a readable charter the user confirms, then arms and runs the loop propose-only under the coco-loops governance framework.

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

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.

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

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

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

Commits, pushes and remotely verifies authorized repository changes; does not create releases.

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

Application Security Posture Management persona. Correlates findings from SAST, DAST, and SCA tools, deduplicates noise, maps vulnerabilities to specific code commits, and generates targeted remediation PRs.

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

Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.

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

Performs security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.

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

Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → pr.

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

Phase-gated commit workflow for clean git history -- implement, review, test, commit per phase

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

Persistent planning system with 3 markdown files (PLAN.md, PROGRESS.md, CONTEXT.md). Use when starting large features, multi-session work, or complex refactoring. Auto-tracks commits in PROGRESS.md.

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

Git Commit Rules

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

Security-focused differential code review with blast radius analysis, risk-adaptive depth (DEEP/FOCUSED/SURGICAL), git history correlation, and structured finding format. Adapted from Trail of Bits. Use when reviewing PRs, commits, or code changes for security implications.

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