autosteer
Run the full development pipeline autonomously without pausing between phases. Stops only on quality-gate failures.
Best use case
autosteer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Run the full development pipeline autonomously without pausing between phases. Stops only on quality-gate failures.
Teams using autosteer should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/autosteer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How autosteer Compares
| Feature / Agent | autosteer | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Run the full development pipeline autonomously without pausing between phases. Stops only on quality-gate failures.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Autosteer Suspends the **pacing rule** from `CLAUDE.md`. Proceed through all phases without confirmation, stopping **only** on quality-gate failures. ## Activation - Do **not** pause between phases or present plans for approval. - **Do** stop on quality-gate failure (`make check`, `make test`, `make test-cov-check`). Attempt fix twice, then stop and report. ## Steps ### 1. Resolve the ticket If argument is a ticket ID (`DBA-XXX`, number, or URL): fetch with `get_issue`, move to **Develop**. If free-text: create via `create_issue` in **DBA** project (derive summary, description, type; default Task). Move to **Develop**. If no argument: ask user once, then proceed autonomously. ### 2. Execute phases Follow **After Completing Work** in `CLAUDE.md` (phases 1-7), with: - Phase 2 (implement): up to two retries on test failure. - Phase 3 (validate): run quality gates per **Quality Gates** in `CLAUDE.md`. Two fix attempts, then stop. - Phase 4 (review): fix Critical/High findings, note Medium/Low. - Phase 5-7: use `create-branch`, `create-pr` skills. Skip pre-push pause. ### 3. Report Output: ticket ID/link, branch name, PR URL, unfixed review findings. ## Guardrails - Never commit or push to `main`. - Never skip quality gates. - Never create a ticket without at least a task description. - Stage specific files -- never `git add -A` or `git add .`. - If `gh` or YouTrack MCP unavailable, stop and inform user.
Related Skills
write-tests
Write or update unit tests for changed code, following project conventions and ensuring coverage meets the 80% threshold.
update-pr
Stage, commit, and push follow-up changes to an existing feature branch or PR. Use for quick iterations.
setup-environment
Set up or verify the local development environment. Use when starting work in a fresh clone or new machine, when commands fail with missing dependencies or broken imports, or before running `make check`/`make test` for the first time in a session.
review-architecture
Review architecture quality, maintainability, and developer experience.
make-yt-issue
Ensure a YouTrack issue exists before starting work. Validates existing tickets or creates new ones.
local-code-review
Review local code changes for correctness, regressions, missing tests, and Databao-specific risks.
eval-skills
Run structured evaluations on skills to measure quality and track improvements.
create-pr
Stage, commit, push, and open a GitHub PR following project conventions. Use when code is ready to ship.
create-branch
Create a feature branch following project naming conventions. Use when starting work on a ticket, after understanding the scope, or when the agent needs to branch off main for new work.
check-pr-comments
Fetch unresolved PR review threads, triage them, implement fixes, validate, reply in-thread, and resolve.
check-coverage
Run test coverage measurement, analyze results, and fix gaps when coverage falls below the 80% threshold.
swe-cli-skills
Senior engineer CLI expertise for AI agents — workflows, safety guardrails, gotchas, and anti-patterns across cloud, IaC, containers, databases, dev tools, and platforms