# Circleci Status

> Check CircleCI build status and failed job logs for the current GitHub repository. Use when asked whether CircleCI is green, failing, pending, or when needing CircleCI job logs.

- Skill: `flurdy/circleci-status` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add flurdy/circleci-status`
- Raw SKILL.md: https://api.skillmd.com/api/skills/flurdy/circleci-status/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: flurdy (https://skillmd.com/u/flurdy)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/flurdy/circleci-status

---


# CircleCI Status

Check the latest CircleCI pipeline/workflow status for the current GitHub repository, with optional failed job logs.

## Authentication

- Basic GitHub commit status/check-run summaries use `gh` when authenticated.
- CircleCI pipeline/workflow/job details use `CIRCLECI_TOKEN` when already set, otherwise `secret-api-key lookup circleci "$SECRET_API_KEY_PROJECT"`.
- CircleCI project slug is derived from `origin`: `gh/{owner}/{repo}`.

Store the token once and expose only its non-secret project selector:

```bash
secret-api-key store circleci flurdy
export SECRET_API_KEY_PROJECT=flurdy
```

## Usage

```bash
/circleci-status          # Summarise latest status for current branch/HEAD
/circleci-status logs     # Show latest failed job logs for current branch
/circleci-status main     # Summarise latest CircleCI pipeline for branch main
/circleci-status logs main
```

## Instructions

Always run the helper scripts fresh; never reuse prior status output.

### Status mode

For no argument, or an argument other than `logs`, run:

```bash
~/.agents/skills/circleci-status/scripts/status.sh {optional-branch-or-ref}
```

Rollout watchers may pass a second exact revision argument. In that mode the helper selects only the
matching branch pipeline and uses the same revision for GitHub status/check fallbacks:

```bash
~/.agents/skills/circleci-status/scripts/status.sh {branch} {sha}
```

Render:

```markdown
## CircleCI status — {repo} `{branch}`

- GitHub commit status: {state}
- GitHub check runs: {counts by conclusion/status}
- CircleCI: {workflow statuses or token-missing note}
```

If `---CIRCLECI-STATUS---` is `NO_TOKEN`, say:

> CircleCI API details unavailable: configure `SECRET_API_KEY_PROJECT` and its CircleCI key. GitHub commit/check status above may still show CircleCI's reported state.

If GitHub status includes CircleCI contexts with `target_url`, include links for failing/pending contexts.

### Logs mode

For `logs` as the first argument, run:

```bash
~/.agents/skills/circleci-status/scripts/logs.sh {optional-branch}
```

Render:

```markdown
## CircleCI logs — {repo} `{branch}`

| Job | Status | Number |
|-----|--------|--------|
```

Then include the tail or relevant failure portion of `---LOGS---`. Keep output concise; prefer the final failing command/error block over dumping thousands of lines. If no token is configured, explain that logs require a CircleCI key for `SECRET_API_KEY_PROJECT`.

## Failure handling

- `NO_GIT_REPO`: say this must be run inside a GitHub-backed git repo.
- `NO_TOKEN`: show GitHub status if available, and explain how to configure the project keyring lookup.
- CircleCI API errors: report the error and fall back to GitHub commit/check status when present.