commit — for Claude Code commit, snyk-ls, community, for Claude Code, ide skills, language-server, Read and follow, implementation, bash pwd, Then run: 1

v1.0.0
GitHub

このスキルについて

適した場面: Ideal for AI agents that need prepare, verify, and commit code changes following project standards. ローカライズされた概要: Language Server used by IDEs as Snyk Backend for Frontends # Commit Workflow Prepare, verify, and commit code changes following project standards. It covers ide, language-server, sast workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

機能

Prepare, verify, and commit code changes following project standards.
Verify → Fix Issues (TDD) → Pre-commit Checks → Commit → Tests → [Push]
Quick Start Checklist
Copy and track progress:
[ ] Step 1: Run verification skill

# 主なトピック

for Claude Code language-server Read and follow implementation bash pwd Then run: 1
snyk snyk
[77]
[15]
更新日: 4/14/2026

Skill Overview

Start with fit, limitations, and setup before diving into the repository.

適した場面: Ideal for AI agents that need prepare, verify, and commit code changes following project standards. ローカライズされた概要: Language Server used by IDEs as Snyk Backend for Frontends # Commit Workflow Prepare, verify, and commit code changes following project standards. It covers ide, language-server, sast workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

このスキルを使用する理由

推奨ポイント: commit helps agents prepare, verify, and commit code changes following project standards. Language Server used by IDEs as Snyk Backend for Frontends # Commit Workflow Prepare, verify, and commit code changes

おすすめ

適した場面: Ideal for AI agents that need prepare, verify, and commit code changes following project standards.

↓ 実現可能なユースケース for commit

ユースケース: Applying Prepare, verify, and commit code changes following project standards
ユースケース: Applying Verify → Fix Issues (TDD) → Pre-commit Checks → Commit → Tests → [Push]
ユースケース: Applying Quick Start Checklist

! セキュリティと制限

  • 制約事項: Generated diagram source (commit PNGs only if needed)
  • 制約事項: Requires repository-specific context from the skill documentation
  • 制約事項: Works best when the underlying tools and dependencies are already configured

About The Source

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Labs デモ

Browser Sandbox Environment

⚡️ Ready to unleash?

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

Boot Container Sandbox

FAQ とインストール手順

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

? よくある質問

commit とは何ですか？

適した場面: Ideal for AI agents that need prepare, verify, and commit code changes following project standards. ローカライズされた概要: Language Server used by IDEs as Snyk Backend for Frontends # Commit Workflow Prepare, verify, and commit code changes following project standards. It covers ide, language-server, sast workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

commit はどうやって導入しますか？

次のコマンドを実行してください: npx killer-skills add snyk/snyk-ls。Cursor、Windsurf、VS Code、Claude Code など19以上のIDEで使えます。

commit の主な用途は？

主な用途は次のとおりです: ユースケース: Applying Prepare, verify, and commit code changes following project standards, ユースケース: Applying Verify → Fix Issues (TDD) → Pre-commit Checks → Commit → Tests → [Push], ユースケース: Applying Quick Start Checklist。

commit に対応するIDEは？

このスキルは 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 に対応しています。統一された導入には Killer-Skills CLI を使えます。

commit に制限はありますか？

制約事項: Generated diagram source (commit PNGs only if needed). 制約事項: Requires repository-specific context from the skill documentation. 制約事項: Works best when the underlying tools and dependencies are already configured.

↓ このスキルの導入方法

  1. 1. ターミナルを開く

    プロジェクトディレクトリでターミナルまたはコマンドラインを開きます。

  2. 2. インストールコマンドを実行

    npx killer-skills add snyk/snyk-ls を実行してください。CLI がIDEまたはエージェントを自動検出し、スキルを設定します。

  3. 3. スキルを使い始める

    このスキルはすぐに有効になります。現在のプロジェクトで commit をすぐ使えます。

! Source Notes

This page is still useful for installation and source reference. Before using it, compare the fit, limitations, and upstream repository notes above.

Upstream Repository Material

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Upstream Source

commit

Install commit, an AI agent skill for AI agent workflows and automation. Explore features, use cases, limitations, and setup guidance.

SKILL.md
Readonly
Upstream Repository Material
The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.
Upstream Source

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):
      - [ ] make test
      - [ ] INTEG_TESTS=1 make test
      - [ ] SMOKE_TESTS=1 make test
- [ ] 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
1make format
2make test
3INTEG_TESTS=1 make test
4SMOKE_TESTS=1 make test

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 (make format shows no changes)
- [ ] 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
1make test
2INTEG_TESTS=1 make test
3SMOKE_TESTS=1 make test

Test Gate Enforcement

Before proceeding to Step 6, verify:

  1. Did SMOKE_TESTS=1 make test complete with all tests passing?
  2. Did INTEG_TESTS=1 make test complete with all tests passing?
  3. Did make test 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

CRITICAL: If tests fail, do not check if they are related to our changes. Identify the root cause and fix it.

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):
- [ ] SMOKE_TESTS=1 make test                    → Smoke tests PASSED

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 & lintmake format
Unit testsmake test
Integration testsINTEG_TESTS=1 make test
Smoke testsSMOKE_TESTS=1 make test
Generate codemake generate
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

関連スキル

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

すべて表示

openclaw-release-maintainer

Logo of openclaw
openclaw

ローカライズされた概要: 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

ローカライズされた概要: Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

ローカライズされた概要: The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 138.4k
⑂ 0
ブラウザ

pr-review

Logo of pytorch
pytorch

ローカライズされた概要: Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review . It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 98.6k
⑂ 0
開発者