Full task-lifecycle skills for Yandex Tracker
yt-bp-claud-code-skills
Seven Claude Code skills that carry a Yandex Tracker issue from plan to merge: estimation, work, review, deploy, tests, merge request
- 1 ★ on the repository
- Last commit
Extended access
Why this level
- Automatically commits, pushes branches and creates merge requests on the user's behalf
- Transitions Tracker issues between statuses on its own without per-step confirmation
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/yt-bp-claud-code-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Automatically commits, pushes branches and creates merge requests on the user's behalf
- Transitions Tracker issues between statuses on its own without per-step confirmation
This is third-party code. Review the repository files before installing.
What it does
The set implements a development pipeline built around a Yandex Tracker issue's status. A single entry point, yt-task-orchestrator, reads the status and a shared agent_meta structure (plan, acceptance criteria, risks, dependencies, status history, attempt counters) and invokes the right stage: planning, implementation, review, docker deployment, testing, and merge request creation plus merging. Status transitions are recorded by the skills themselves in agent_meta.status_history, and once an attempt limit is exceeded (more than three) a skill comments on the issue and stops the cycle. The pipeline relies on a separate yandex-tracker-mcp server for Tracker access and a repository tool such as claude-glab-skill for merge requests.
Who it is for. For teams that already run a development pipeline around Yandex Tracker statuses and want to automate the transitions between its stages.
Good fit when
- You already have a Yandex Tracker MCP server and a merge-request tool
- Your team's process matches the status chain in the README: estimation, work, review, deploy, tests, release
- You want a single orchestrator that picks the next stage from the issue's status
Not a fit when
- Your Tracker status model differs from the chain hardcoded in the skills
- You have no separate Tracker MCP server and merge-request tool, the skills do not work without them
Example request
Take issue PROJ-123 through the pipeline: from estimation to merge requestLimitations
The status chain and escalation rule (mentioning a specific person when the attempt limit is exceeded) are hardcoded for the author's process and need rewriting for another team. No built-in Tracker integration: an external yandex-tracker-mcp is required. A merge-request tool is not included.
How to disable. Remove the skill folders (yt-task-orchestrator and the other yt-task-* skills) from ~/.claude/skills.
FAQ
What happens on a test-stage failure?
The attempts.test counter increases, last_error is filled with the stage and message; past three attempts a comment is added to the issue and the cycle stops.
Which Tracker MCP should be used?
The README references yandex-tracker-mcp@latest as the external dependency for issue access.
Discussion
No questions or reviews yet.
Related
All Yandex Tracker toolsYandex Tracker skill on the official Python client
Yandex Tracker Skill
A skill for Claude Code, Codex and Gemini CLI on top of the official yandex_tracker_client package: search, issues, statuses, sprints, bulk edits
YaTracker: Yandex Tracker skill
YaTracker
A Claude Code skill for Yandex Tracker with a board overview, issue statistics and self-learning memory about your organization's patterns
A Claude Code plugin for Yandex Tracker and Wiki backed by the yandex-cli binary: 16 commands with output tuned for agent reading
A Yandex Tracker CLI built for LLM agents: issues, comments, worklogs, checklists and bulk operations, with an agent skill
Yandex Tracker CLI
tracker
The tracker command-line tool for Yandex Tracker with JSON output and a ready SKILL.md workflow for agents
A Yandex Tracker skill for Claude Code, invoked with /tracker, optionally gathering context from your codebase
README in short
The Russian README describes the seven pipeline skills, the issue status chain, a shared agent_meta structure with plan, acceptance criteria, risks and attempt counters, a retry policy with escalation, and each stage's responsibility from planning to merge request.