commit — ide-plugin commit, snyk-intellij-plugin, community, ide-plugin, ide skills, intellij, intellij-plugin, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Perfect for Code Management Agents needing standardized commit workflows with IntelliJ platform integration. Snyk Vulnerability Scanner for IDEs based on the IntelliJ platform

# Core Topics

snyk snyk
[65]
[35]
Updated: 2/27/2026

Agent Capability Analysis

The commit skill by snyk is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance. Optimized for ide-plugin, intellij, intellij-plugin.

Ideal Agent Persona

Perfect for Code Management Agents needing standardized commit workflows with IntelliJ platform integration.

Core Value

Empowers agents to enforce project standards through automated verification, TDD issue fixing, and pre-commit checks using tools like Snyk Vulnerability Scanner, leveraging protocols such as Git for version control and Gradle for test suite execution.

Capabilities Granted for commit

Automating commit validation with Snyk Vulnerability Scanner
Generating atomic commits following project standards
Debugging code issues using Test-Driven Development (TDD)

! Prerequisites & Limits

  • Requires IntelliJ platform IDE
  • Dependent on Gradle for test execution
  • Limited to Git version control system
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

commit

Install commit, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly

Commit Workflow

Prepare, verify, and commit code changes following project standards.

Workflow Overview

Verify → Fix Issues (TDD) → Pre-commit Checks → Commit → Tests → [Push]

Quick Start Checklist

Copy and track progress:

Commit Progress:
- [ ] Step 1: Run verification skill
- [ ] Step 2: Fix issues using TDD
- [ ] Step 3: Run pre-commit checks
- [ ] Step 4: Create atomic commit
- [ ] Step 5: Run ALL test suites (3 REQUIRED):
      - [ ] ./gradlew ktlintCheck spotlessApply
      - [ ] ./gradlew koverXMLReport
      - [ ] ./gradlew verifyPlugin
- [ ] Step 6: Push (optional, ask first)

CRITICAL: Step 5 has THREE mandatory test suites. Skipping any is FORBIDDEN.


Step 1: Run Verification Skill

Execute the verification skill to analyze code changes:

Verification Progress:
- [ ] Load project rules and standards
- [ ] Trace code paths for modified files
- [ ] Check for semantic changes
- [ ] Identify code smells
- [ ] Run security scans
- [ ] Review PR feedback (if PR exists)

Read and follow: .cursor/skills/verification/SKILL.md

Output: List of issues found, categorized by severity.


Step 2: Fix Issues Using TDD

For each issue identified by verification:

TDD Gate (MANDATORY)

Before ANY fix:

  • Write failing test first
  • Confirm test fails without fix
  • Implement minimal fix
  • Confirm test passes

Never skip TDD. Use implementation skill for complex fixes.

Issue Priority

  1. Security vulnerabilities - Fix immediately (except test data)
  2. Breaking changes - Confirm intentional, add tests
  3. Code smells - Fix immediately
  4. PR feedback - Address blockers first

Step 3: Pre-commit Checks

Run:

bash
1./gradlew ktlintCheck spotlessApply 2./gradlew koverXMLReport 3./gradlew verifyPlugin

Security Scans

Get absolute path first:

bash
1pwd

Then run:

  1. snyk_sca_scan with absolute project path
  2. snyk_code_scan with absolute project path

Fix any security issues (skip test data false positives).


Step 4: Create Atomic Commit

Pre-commit Verification

- [ ] Linting clean (./gradlew ktlintCheck spotlessApply)
- [ ] Security scans clean
- [ ] No implementation plan files staged
- [ ] Documentation updated (if needed)

Commit Format

type(scope): description [XXX-XXXX]

Body explaining what and why.

Types: feat, fix, refactor, test, docs, chore, perf

Extract issue ID from branch:

bash
1git branch --show-current

Staged Files Check

bash
1# Review what will be committed 2git status 3git diff --staged

Never commit:

  • Implementation plan files (*_implementation_plan/)
  • Secrets or credentials
  • Generated diagram source (commit PNGs only if needed)

Execute Commit

bash
1git add <files> 2git commit -m "$(cat <<'EOF' 3type(scope): description [XXX-XXXX] 4 5Body explaining what and why. 6EOF 7)"

NEVER use --no-verify. NEVER amend commits.


Step 5: Run All Test Suites (After Commit, Before Push)

CRITICAL: ALL three test suites MUST be executed after commit but before push. Skipping ANY test suite is FORBIDDEN.

Execution Order

Run these commands IN ORDER and wait for each to complete:

bash
1./gradlew ktlintCheck spotlessApply 2./gradlew koverXMLReport 3./gradlew verifyPlugin

Test Gate Enforcement

Before proceeding to Step 6, verify:

  1. Did ./gradlew ktlintCheck spotlessApply complete with all tests passing?
  2. Did ./gradlew koverXMLReport complete with all tests passing?
  3. Did ./gradlew verifyPlugin complete with all tests passing?

If ANY answer is "no" or "I didn't run it", STOP and run the missing tests.

Test Failure Protocol

If tests fail:

  1. Do not proceed to push
  2. Identify root cause
  3. Apply TDD fix (test first, then implementation)
  4. Create new commit with fix
  5. Re-run ALL test suites (not just the one that failed)
  6. Continue only when ALL three test suites pass

Step 6: Push (Optional)

Mandatory Test Checklist

You MUST run each test suite and check it off. Do NOT proceed to push until ALL boxes are checked:

Test Suite Checklist (ALL REQUIRED):
      - [ ] ./gradlew ktlintCheck spotlessApply
      - [ ] ./gradlew koverXMLReport
      - [ ] ./gradlew verifyPlugin

Always ask before pushing.

If approved:

bash
1git push --set-upstream origin $(git branch --show-current)

After Push

Offer to:

  1. Create draft PR (if none exists)
  2. Update PR description (if PR exists)
  3. Check snyk-pr-review-bot comments
  4. Run sleep for 60s
  5. Read and run verification skill

Command Reference

TaskCommand
Format & lint./gradlew ktlintCheck spotlessApply
Unit tests./gradlew test
Integration tests./gradlew verifyPlugin
SCA scansnyk_sca_scan with absolute path
Code scansnyk_code_scan with absolute path
Current branchgit branch --show-current
Pushgit push --set-upstream origin $(git branch ...)

Red Flags (STOP)

  • Tests failing
  • Any test suite skipped
  • Security vulnerabilities unfixed
  • Implementation plan files staged
  • Unresolved PR blockers
  • TDD not followed for fixes
  • --no-verify being considered

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is commit?

Perfect for Code Management Agents needing standardized commit workflows with IntelliJ platform integration. Snyk Vulnerability Scanner for IDEs based on the IntelliJ platform

How do I install commit?

Run the command: npx killer-skills add snyk/snyk-intellij-plugin. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for commit?

Key use cases include: Automating commit validation with Snyk Vulnerability Scanner, Generating atomic commits following project standards, Debugging code issues using Test-Driven Development (TDD).

Which IDEs are compatible with commit?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for commit?

Requires IntelliJ platform IDE. Dependent on Gradle for test execution. Limited to Git version control system.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add snyk/snyk-intellij-plugin. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use commit immediately in the current project.

Related Skills

Looking for an alternative to commit or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

149.6k
0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

138.4k
0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI