Loading...
Loading...
Found 34 Skills
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".
Analyze changes and update WordPress plugin version references safely.
This skill must be loaded via the skill tool when the user mentions anything related to publishing or release an npm package. It contains essential knowledge about the complete release workflow. Things a user might say are Publish the npm package,Release a new version,Deploy to npm,Create a new release,Bump the version and publish
Expert in Gravito Satellite modules. Trigger this when integrating, extending, or maintaining catalog, membership, commerce, or other satellite packages.
Guidance for writing git commit messages that follow the Conventional Commits 1.0.0 specification. Use when preparing commit messages, summarizing code changes for a commit, or validating commit text for compliance.
Documentation standards for changelogs, feature specs, and module documentation
Writes and reviews Conventional Commits commit messages (v1.0.0) to support semantic versioning and automated changelogs. Use when drafting git commit messages, PR titles, release notes, or when enforcing a conventional commit format (type(scope): subject, BREAKING CHANGE, footers, revert).
Complete changelog and release notes infrastructure. Audits current state, implements missing components, and verifies the release pipeline works end-to-end.
Changelog generation, release notes, and semantic versioning. Use when user asks to "write a changelog", "generate release notes", "bump version", "follow conventional commits", "create a release", "update CHANGELOG.md", or any versioning and release documentation tasks.
Generate and maintain changelogs following Keep a Changelog and Conventional Commits standards. Use when releasing versions, documenting changes, or updating project history.