Runs lint, type-check, and test gates before pushing a branch and opening a pull or merge request.
npx skills add https://github.com/Yassimba/loom --skill release-yassimba
Please help me install this Agent Skill. Skill: release Source: https://github.com/Yassimba/loom/tree/main/skills/release Command: npx skills add https://github.com/Yassimba/loom --skill release-yassimba
gh) or GitLab (glab) from the git remote, pushes the branch, and opens a PR/MR with a Conventional Commits title and a ticket-derived body. - Release notes drafting: Classifies commits into highlights, breaking changes, features, and fixes, and drafts changelog entries matching the repo's existing format. - Use Case: After finishing a feature branch, ask the agent to release it — it discovers the project's check commands, fixes any lint or test failures, commits with confirmation, pushes, and opens a merge request whose Summary and Test Plan come from the branch's tickets. ## Quick Start Use the release skill to run the project checks, push this branch, and open a pull request.High-intent search queries and answers about installing and using this skill.
Use the GitHub CLI with `gh pr create --title <t> --body <b> --base <base>` after pushing your branch. On GitLab, the equivalent is `glab mr create --title <t> --description <b> --target-branch <base>`.
Discover the project's own commands from files like package.json, pyproject.toml, Cargo.toml, or a Makefile, then run lint, type-check, and tests in that order. Each phase must pass with fresh output before moving to the next.
Yes. The forge is detected from the git remote URL: github.com maps to the gh CLI and hosts containing gitlab map to glab, including self-hosted instances listed in either CLI's auth status. If neither CLI knows the host, it runs headless and prints the branch name.
No. Suppressions like `# noqa`, `eslint-disable`, or `# type: ignore` are prohibited by default; violations must be fixed in the source. A suppression is only allowed after explicitly asking the user and receiving approval with a justification comment.
Small obvious failures such as typos or broken imports are fixed directly and re-run. Substantive failures stop the workflow and offer options to investigate via the diagnosing-bugs skill, abort the release, or show the failure output.
The body is built from the branch's tickets on the configured issue tracker. Summary bullets reference issues with closing keywords like Closes #N, and the Test Plan is derived from each ticket's acceptance criteria.
TMI-appsValidate and push committed Git changes to a remote repository.
devbasexDelete merged branches and worktrees with approval, then update the base branch.
KSD-CODiagnose bugs through root-cause investigation, pattern analysis, and hypothesis testing.
skaile-aiOpen a draft GitHub pull request from the current feature branch using the gh CLI.