Your agent can do more. Find the skill that makes it happen.
Find your next superpower If you are an agent, refer to our llms.txt for full access.Sync the current working branch with origin/main and optionally resolve merge conflicts. Use when synchronizing local branch with the latest changes from main, with automatic or manual conflict resolution.
Git-гигиена и релизная дисциплина — Conventional Commits (таблица типов, BREAKING CHANGE), semver-правила бампа, поимённые коммиты и запрет `git add .`/`git add -A` при параллельных сессиях, ловушка squash-merge долгоживущей ветки (`git merge-base --is-ancestor`, рецепт `git merge -s ours`), worktree для параллельной работы, запрет force-push и push без явного подтверждения. Use для коммитов, PR, changelog, версионирования и релизов.
Structure git work with atomic commits, conventional messages, short-lived branches, and pre-commit hygiene. Load when committing, branching, resolving merge conflicts, organizing parallel work, or reviewing git history. Also triggers on "git workflow", "commit message", "conventional commits", "atomic commit", "branch strategy", "git worktree", "how should I commit this". Does not replace project…
commits, PRs and releases. Primary owner: git and release workflow. Do not use for: product code. Use when this role is selected by the Agent-Vorcl-Flow router.
Read-only аудит git-истории — нарушения Conventional Commits, гигантские коммиты-свалки, большие бинарники, ветки-сироты. Use when нужно проверить гигиену репозитория (gitflow)
CHANGELOG.md по Keep a Changelog из истории коммитов между тегами — рубрики Added/Fixed/Changed/Breaking. Use when нужно собрать или обновить changelog (gitflow)
Поимённый коммит по Conventional Commits — сам проверь git status, файлы явно, чужой WIP не трогать. Use when нужно закоммитить изменения (gitflow)
Ветка → поимённые коммиты → PR через gh CLI/GitHub MCP — заголовок по конвенции, описание что/зачем/как проверено. Use when изменения нужно оформить в pull request (gitflow)
Релиз по semver — версия из коммитов → синхронизация манифестов → tag → GitHub release; push и публикация ТОЛЬКО с явного подтверждения. Use when нужно выпустить версию (gitflow)
Цель роли gitflow: session-first план, реализация в разрешённом scope и независимая проверка; Task Master только по явному выбору.
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not c…
Use when hunting GitHub Actions cache poisoning vulnerabilities where an attacker can inject malicious content into the CI/CD cache and have it restored by a privileged downstream workflow. Trigger on: "cache poisoning", "actions/cache", "actions/setup-node", "node_modules cache", "GitHub Actions cache", "pnpm cache", "LRU eviction", "10GB limit", "Cacheract", "poisoned cache", "workflow cache att…
Skills give your agent reusable instructions for a specific job. Pick one, read what it does, and bring it into your workflow.
A name only tells half the story. Search the full description and instructions to find the right fit.
Read the skill, visit its source, and see exactly what you’re adding to your agent.
Copy the install command from a skill page and run it in your project.
npx skillycli add owner/repo --skill name