Menu
Create consistent releases and changelogs
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create git commits using goji rules from .goji.json (type/scope/emoji/signoff) with path-based heuristics.
Skill para registrar worklogs en Jira usando el issue key derivado del branch actual y una descripcion basada en los commits del branch.
Skill para listar issues no terminadas asignadas al usuario en Jira usando `jasper.toml`, elegir una y crear un branch `feature/<ISSUE-KEY>`.
Skill para generar un reporte de implementacion para el issue de Jira derivado del branch actual usando un template y un resumen basado en commits, y publicarlo como comentario.
Skill para crear issues de tipo epic y/o task en Jira Cloud a partir de un archivo Markdown y luego completar componentes, labels y issue keys.
Validate, push the current branch, and create a GitLab merge request from the current diff
| name | git-release |
| description | Create consistent releases and changelogs |
| license | Proprietary |
glab release create commandUse this when preparing a tagged release. Ask clarifying questions if versioning scheme is unclear.
task validategit log --oneline $(git describe --tags --abbrev=0)..HEADUse .gitlab/merge_request_templates/MERGE_REQUEST_TEMPLATE.md as the base for the MR body and fill it with the specifics of the change.
Prefer to include:
task validateExample (copy/paste):
glab mr create --target-branch main --source-branch "${BRANCH}" \
--title "<title>" \
--description "$(cat <<'EOF'
## Proposed changes
<describe the big picture and link issues>
Testing:
- `task validate`
Migration steps (if any):
- None
Screenshots:
- [ ] N/A
- [ ] <paste screenshot 1>
## Types of changes
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
## Checklist
- [ ] I have read the [CONTRIBUTING](/docs/contributing.md) doc
- [ ] Lint and unit tests pass locally with my changes
- [ ] I have added tests that prove my fix is effective or that my feature works
- [ ] I have added necessary documentation (if appropriate)
- [ ] Any dependent changes have been merged and published in downstream modules
## Further comments
<optional>
EOF
)"
Example release command:
glab release create <tag> --notes-file <notes-file>