.claude/skills/git-commit-creator/SKILL.md
Creates properly formatted Git commits following conventional commit standards for the MCPSpy project. Use when asked to commit changes, stage files, or manage git workflows. Has access to git status, diff, checkout, add, and commit commands.
npx skillsauth add alex-ilgayev/mcpspy git-commit-creatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Automates the creation of well-structured Git commits for the MCPSpy project.
You should STRICTLY follow the following steps:
git status, git diff and git diff --staged.git checkout -b <branch-name>, create concise branch name with standard prefixes (e.g., feat, chore, fix).git commit -m "<commit-message>", create a conventional commit message that accurately reflects the changes.feat(component):, chore:, fix(component):library-manager, ebpf, mcp, http, outputfeat(library-manager): add support for container runtime detectionchore: update dependencies to latest versionsfix(ebpf): handle kernel version compatibility issuesdevelopment
Use this agent when working with prompt injection detection integration tests, including running tests, debugging failures, or adding new test samples.
tools
Handles all Golang testing tasks including running tests, writing new tests, and fixing test failures. Follows MCPSpy testing conventions with require for critical assertions and assert for non-critical ones.
tools
Creates well-structured GitHub issues for the MCPSpy project using the gh CLI tool. Use when asked to create issues, report bugs, or document features. Follows conventional naming with feat/chore/fix prefixes and maintains appropriate detail levels.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.