Results for “gated-commit”

6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.

Executes containment strategies to stop active adversary operations and prevent lateral movement during a confirmed security breach, using network segmentation, endpoint isolation, credential revocation, and access control modifications.

Creates standardized git commits using the Conventional Commits specification by analyzing the diff, staging files, and generating appropriate commit messages.

Turns working-tree changes into well-formed local commits following Conventional Commits, with atomic boundaries and issue references.

Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

Stages and commits changes with quality checks, status review, and a clear message, then shows recent history.

Capabilities

Generate conventional commit message suggestions for staged git changes, aligned with the repository's commit style. Use when the user wants a commit message suggestion, asks what to commit, or says "suggest commit".

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Creates atomic git commits with terse, exact Conventional Commits messages, splitting changes by concern and staging files individually.

Create standardized, semantic git commits using the Conventional Commits specification by analyzing diffs to determine type, scope, and message.

Create commits following Sentry conventions with proper format, issue references, and AI attribution.

Bootstraps AGENTS.md and CLAUDE.md for AEM 6.5 LTS projects, tailored to project structure and detected add-ons.

Generate a Conventional Commits message from staged changes and wait for confirmation before committing. Use when the user asks to commit or generate a commit message.

Fact-forcing gate that blocks Edit/Write/Bash (including MultiEdit) and demands concrete investigation (importers, data schemas, user instruction) before allowing the action. Measurably improves output quality by +2.25 points vs ungated agents.

Executes small ad-hoc tasks with GSD guarantees, spawning planner and executor agents, tracking tasks in .planning/quick/, and updating STATE.md. Supports composable flags for discussion, research, plan-checking, and verification.

Create commits following Sentry conventions with proper conventional commit format and issue references, including branch safety checks.

Blocks Edit/Write/Bash actions until the agent presents concrete facts about imports, data schemas, and the user's instruction, improving output quality.

Creates clean, conventional git commits using standard git. Use when the user asks to "commit", "git commit", "create commit", or wants to commit staged or unstaged changes.

Fact-forcing gate that blocks Edit/Write/Bash (including MultiEdit) and demands concrete investigation (importers, data schemas, user instruction) before allowing the action. Measurably improves output quality by +2.25 points vs ungated agents.

Read-only audit of product-analytics instrumentation: event taxonomy, funnel completeness, consent-gated firing, dead/duplicate/phantom events. Use when "audit our analytics", "are we tracking the right events", "funnel instrumentation", or before iterate-post-launch. PostHog/Amplitude/Mixpanel/GA4.

Create repository-adaptive checkpoint commits for coherent work, including requests to split changes into commits and push; publication remains separately authorized

Collects publicly available information about a target organization to identify attack surfaces, social engineering targets, technology stacks, and credential exposures for authorized security testing.

ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.

Consolidates 89 high-integrity SOPs for the Full department of the Galyarder Framework, covering adapter creation, execution protocols, and multi-agent hygiene.

Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue re...

Gated PRD generation — interrogates problem, user, and metric before drafting; refuses to draft on unknowns. Usage: /prd <feature-or-problem>

Generates user-facing changelogs for stable releases of the Galyarder Framework, following calendar versioning and including breaking changes, highlights, improvements, fixes, and contributor attribution.

Google Tag Manager expertise. Audit GTM containers, design tag and trigger architecture, debug firing issues, implement consent mode v2, and advise on server-side tagging. Use when the user asks about GTM, tag management, container audits, consent mode, server-side tagging, or tracking implementation.

Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy. Use when PR preparation or commit strategy is needed.

Orchestrates multi-agent project builds with persistent state, parallel execution, and atomic git commits.

Creates commits following Sentry conventions with conventional commit format and issue references.

Rolls back Open-workspace phase or plan commits using a phase manifest with dependency checks and a confirmation gate, preserving history via git revert.