Loading...
Loading...
Found 26 Skills
Use git to commit code in the current repository. This skill is used when the user requests to submit code, write commit messages, execute git commit/push/amend, or mentions terms like submit, commit, push, stage and commit, save changes, create a commit, or when directly specified by a sub-agent.
Create one or more Conventional Commits following the spec and push the current branch. Use when the user asks to create commits, write a conventional commit message, commit and push changes, or prepare commits before opening a pull request.
Push commits and create/update pull request
Fetch upstream, rebase, stage all changes, run ADR compliance check on modified artifacts, generate a descriptive commit message from the diff, commit, and push to the current branch's upstream. Handles merge conflicts by preferring local changes for config/project files and upstream for scaffolding.
Utiliza esta habilidad para analizar cambios locales en el repositorio Git, redactar mensajes de commit profesionales en español y ejecutar commit/push de forma segura.
Commit and push vault changes to Git with smart commit messages. Auto-stages files, creates meaningful commits, and syncs with remote. Use after making vault changes or at end of day.
Open every hackathon working session. Reads the event clock first and says the time left to the build end and the freeze, runs hackathon doctor and walks the participant through every failed check, restarts the team app when it is down, confirms the platform received the last push, keeps the team's project description current, and sets the pacing for the rest of the session (small pushes, the 60/30/15-minute warnings, fixes only in the grace, the demo deck before the end). Use at the start of any session in a team repository, and when the participant says "check", "is my setup ok", "the app is down", "doctor", "how much time is left", "when is the freeze", "did my push count", "our idea changed", or when something in the setup looks wrong.
Quick commit and push with minimal, clean messages
Commit and push ALL changes (staged + unstaged + untracked) to the remote repository
Analyzes the working tree, writes a Conventional Commit message, then commits and pushes. Invoked manually only.
Turn a committed branch into a merge request in GitLab through the glab CLI: push it, write the title and description from the commits, and give back the link. Trigger on «создай MR», «оформи мерж реквест», «запушь и создай MR», «на ревью», create MR, merge request, open a PR. Expects the work to be committed already — committing is the commit skill, and reviewing somebody else's MR is review-mr.
Push the current branch to origin safely (lint, test, resolve non-fast-forward via pull skill, then push). Use when the user asks to push or publish commits to the remote. Does not create or edit PRs—use the create-pr-jp skill for that.