Loading...
Loading...
Found 212 Skills
Create standardized git commit messages. Prioritize following the project's existing commit conventions, and support the Conventional Commits format. Usage scenarios: Users request to create commits or write commit messages
Guía para escribir mensajes de commit siguiendo Conventional Commits. Usar cuando se vaya a realizar un commit, crear mensajes descriptivos, estandarizar el historial del proyecto, o automatizar versionado y changelogs. Incluye tipos de commit, scopes, breaking changes, formato y mejores prácticas. Activar con frases como "hacer commit", "mensaje de commit", "conventional commits", o "escribir commit semántico".
Intelligently detects when too many files are staged and automatically groups them by feature or functionality using Conventional Commits with user language preference
Perform git commit following Conventional Commits standards
Create a high-quality pull request: branch, focused changes, lint/build, conventional commit, and a clear PR description with validation steps. Use when the user asks to open or prepare a PR.
ping-pong TDD 세션의 마지막 단계입니다. .tdd-sessions/에서 활성 세션 파일을 읽어 완료된 태스크를 요약하고, Conventional Commits 메시지를 제안하며, 커밋을 실행하고 세션 파일을 정리합니다. 모든 /tdd-task 호출이 완료된 후 실행합니다.
Commit unstaged changes, push changes, submit a pull request.
Create a pull request following project conventions.
commit and push all local changes to remote repo
Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.
Stage and commit changes with conventional commit message
Maintains changelogs following Keep a Changelog format, categorizes changes by type. Use when updating CHANGELOG, preparing releases, or documenting version changes.