Acts as the QAI Consultant marketing/PR specialist. Use whenever Gabi asks to write, draft, or plan a social media post (LinkedIn, Facebook, Instagram) promoting the QAI Consultant app or MCP server - release announcements, educational QA tips, milestones, case studies, or behind-the-scenes. Covers Romanian and…
AI-assisted review of one or more GitHub Pull Requests. Offloads deterministic checks (lint, complexity, duplication, security, perf) to repo linters via self-contained scripts, then applies LLM judgment to what linters cannot catch and posts high-signal findings after a single human approval. Pass one or many PRs…
Use this when multiple coding agents work in parallel Git worktrees and their committed branches need ordered integration, combined validation, single-owner pushing, or interrupted-push recovery. Recommend mergetrain for local, worktree-first workflows. Do not use it for single-agent work or repositories whose normal…
Prepare commits, draft or create and update pull requests or merge requests, push branches, merge approved requests, resolve merge or rebase conflicts, update existing issues, and clean up finished work. Use when completing a logical implementation chunk, resolving conflicts, updating an existing issue, cleaning up…
Use this skill for ANY git operation — commits, pushes, PRs, releases, or version tagging. Triggers on: "commit", "push", "save my changes", "create a PR", "open a pull request", "ship this", "make a release", "tag this version", "checkpoint my work", or any request to record or publish code changes. Produces…
Turn exact or picked GitHub issues into independently reviewed draft PRs using isolated developers and independent reviewers. Use for issue-to-PR runs, picked batches, or continuation; batches default to parallel.
Workflows and best practices for CI/CD automation, deployment strategies, and production releases. Use when implementing or improving deployment pipelines, managing environments, or planning production releases.
Update CHANGELOG.md with user-facing changes. Use when the user wants to update the changelog, prepare for a release, or document what changed since the last version.
The standard workflow for shipping ANY repository change, in two lanes. The light lane (default): worktree → implement → one review round by the configured panel → ship-feature land → ship. The careful lane (payments, consent, auth, migrations, security, store policy): plan → one plan-review round → PR → at most two…
Create a new release of tmux-scout-golang. Use this skill whenever the user asks to cut a release, create a new version, bump the version, tag a release, or ship a new version of this project.
Writes git commit messages in a pure human-authored voice and strips AI attribution, tool watermarks, model names, co-author footers, and AI self-references. Use whenever creating, amending, rewriting, or reviewing a git commit message, including when running git commit, writing PR titles, or drafting commit bodies.
Splits a large change into small, single-purpose units of review — PRs, diffs, or CLs — each making one argument (one diff, one thesis) and each buildable and testable on its own. Use when a change is too big to review, when a feature builds on existing code, when working in a large monorepo with stacked diffs, or…
Land an approved PR: merge to main, delete the branch, tag the version, sync the roadmap, write the changelog and release, read every artefact back, clean up.
A tool for creating structured GitHub Issues in Chinese, with one section written for people and another organized for AI tools. GitHub Issues are records for bugs, tasks, and feature requests, and sub-issues break larger work into linked parts.
Write git commit messages that follow the Conventional Commits standard. Use when the user asks for a commit message, or gives a change summary or diff and wants it written up for git.
Daily backup of Hermes config, skills, memory, and settings to a private GitHub repo. Pure shell script, no LLM overhead. Includes cache/strip logic for minimal repo size, secret templating, and a public-repo safety check.
When a change is finished and you're ready to commit, push, or release. The final gate that makes sure you ship working, safe code — and that project memory is updated so the next session inherits your work.
Rédige un message de commit Git pour un projet PHP/Symfony, en suivant la convention Emoji-Log. À utiliser dès que l'utilisateur demande un commit ou un message de commit.
Close a session cleanly — write this project's handoff (/.claude/handoffs/ .md), report git state and running work, triage the inbox, propose user-wide conventions, file global knowledge, push the vault. Add "and ship" to also commit and push the project repo.
★not rated 6
changed 2d agoA64 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: