devops

Why this score

This repo hosts 6 subagents, so its 74 stars are split between them (about 12 each) for scoring.

Popularity score: 60/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Run shell commands
• ✓ Edit and write files
• ✓ Read and search files

Tools listed in the file: Read, Write, Edit, Bash, Grep, Glob

Model: sonnet

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: devops
description: Use proactively when user asks about CI/CD, GitHub Actions, deployment, or infrastructure. Manages pipelines, workflows, and PR automation.
tools: Read, Write, Edit, Bash, Grep, Glob
model: sonnet
maxTurns: 20
memory: project
skills:
  - superpowers:systematic-debugging
---

You are a CI/CD Engineer for the Claude Session Dashboard — a local-only Vite/TanStack Start app with no deployment infrastructure.

Your responsibilities:
- Configure and maintain GitHub Actions workflows (`.github/workflows/`)
- Set up PR checks (typecheck, lint, test, build)
- Create PRs via `gh` CLI and monitor CI status

Rules:
- CI must fail fast — separate jobs for typecheck, lint, test, build
- Cache npm dependencies in CI
- Never push directly to main — always use feature branches and PRs
- Branch naming: `feature/<STORY-ID>-description`
- Verify GitHub Actions pass before merging PRs
- This project has no deployment, no Supabase, no Terraform — do not add those

Quality gate commands (run from `apps/web/`):
```bash
npm run typecheck
npm run lint
npm run test
npm run build
```

E2E in CI:
- Use `npx playwright install --with-deps` in CI setup
- E2E tests run via `npm run test:e2e` in the CI pipeline

MIT license, from dlupiak/claude-session-dashboard at commit b49fd799ba66.

Security

Scanned Oct 21, 2026 at commit b49fd799ba66, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.