Results for “gated-commits”

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

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.

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.

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.

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.

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

Defines a protocol for agents to make cryptographically enforced commitments with tiers for ethical, financial, and confidential promises, including execution steps.

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

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.

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

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

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...

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.

Quality Gates

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.

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".

Runs before every git commit on heleni-memory. Checks: no credentials in tracked files, no oversized files, valid SKILL.md frontmatter for any new/modified skill. Triggers: "commit", "before push", "validate repo", or auto-runs as a git pre-commit hook.

Composite skill — take a PR from "I think it's ready" to merged with full gate verification. Chains pr-merge-readiness (verdict) → ci-watch / gh-fix-ci (if blockers) → gh-address-comments (if review needed) → ship (when verdict is MERGE). Use as the one-call answer to "can I merge this?" instead of running 4 skills sequentially.

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

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.

Terse conventional commits. Trigger: commit, git commit, /ijfw-commit

Load this skill when the user says "close milestone", "close-milestone", or "/close-milestone". Creates the milestone-to-master PR, launches the close-milestone-watch command, and orchestrates the end of a milestone cycle.

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

当需要克服拖延、激发最大行动力以完成一项重大挑战或转型时

Enforces a mandatory pre-commit/pre-PR testing gate: detects the test stack, runs the full suite, fixes failures, creates minimal tests when none exist, and verifies coverage before allowing commits.

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

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

Creates atomic git commits with terse Conventional Commits messages and pushes them to the remote, splitting changes by concern and avoiding secret files.

Defines a gated Research-Plan-TDD-Review-Commit pipeline for orchestrating feature development, defect fixes, and refactoring tasks through composable phases and human approval gates.