use-teamcity

name

use-teamcity

description

Interact with the kotlinx-rpc TeamCity CI/CD project using the `teamcity` CLI. Use this skill whenever the user wants to trigger builds, check build status, view build logs, monitor failures, manage the build queue, inspect agents, or do anything related to TeamCity CI. Also use it when the user mentions "TC", "TeamCity", "CI build", "run build", "build status", "build log", "trigger build", "check CI", or references a build configuration name or ID. Trigger even if the user doesn't say "TeamCity" explicitly -- if they ask about CI status, build failures, or want to run something on CI rather than locally, this is the right skill. Do NOT use this skill for local Gradle builds -- use `running_gradle_builds` or `running_gradle_tests` instead.

TeamCity CLI for kotlinx-rpc

Interact with the kotlinx-rpc TeamCity project via the teamcity CLI (expected to be installed at /opt/homebrew/bin/teamcity).

For local Gradle builds and tests, use running_gradle_builds / running_gradle_tests skills instead.

Agent workflow override

When this skill is invoked from the fix-issue skill (autonomous issue-fixing workflow), never run teamcity auth status or teamcity auth login. Instead, prefix every teamcity command with TEAMCITY_TOKEN=$TEAMCITY_AGENT_TOKEN. The fix-issue skill's Authentication section has full details. Outside of fix-issue, the defaults below apply.

Prerequisites

Before running any commands, verify authentication:

teamcity auth status

If not authenticated, the user needs to log in interactively -- suggest they run ! teamcity auth login in the prompt so the browser-based auth flow works in their session.