Check CI, the automated checks run on code changes, for the current branch alongside recent commits. Supports GitLab CI and GitHub Actions, with optional pull request or merge request numbers and links when command-line tools are unavailable.
Show current pipeline status for the active branch (GitLab CI or GitHub Actions)
Review the instructions the agent will receive before you install.
Quick snapshot of the CI pipeline on the current branch.
# 1. Current branch
BRANCH=$(git branch --show-current)
echo "Branch: $BRANCH"
# 2. Last commits
git log -3 --oneline
# With glab CLI (recommended)
if command -v glab &>/dev/null; then
glab ci status --branch "$BRANCH"
else
# Fallback: show URL
REMOTE=$(git remote get-url origin 2>/dev/null || echo "")
if [ -n "$REMOTE" ]; then
WEB_URL=$(echo "$REMOTE" | sed 's/git@gitlab\.com:/https:\/\/gitlab.com\//' | sed 's/\.git$//')
echo "Pipeline: $WEB_URL/-/pipelines?ref=$BRANCH"
fi
fi
# If MR number provided
if [ -n "$ARGUMENTS" ] && command -v glab &>/dev/null; then
glab mr view "$ARGUMENTS"
fi
# With gh CLI (recommended)
if command -v gh &>/dev/null; then
gh run list --branch "$BRANCH" --limit 5
else
# Fallback: show URL
REMOTE=$(git remote get-url origin 2>/dev/null || echo "")
if [ -n "$REMOTE" ]; then
WEB_URL=$(echo "$REMOTE" | sed 's/git@github\.com:/https:\/\/github.com\//' | sed 's/\.git$//')
echo "Actions: $WEB_URL/actions?query=branch%3A$BRANCH"
fi
fi
# If PR number provided
if [ -n "$ARGUMENTS" ] && command -v gh &>/dev/null; then
gh pr checks "$ARGUMENTS"
fi
Branch: feat/add-payment-retry
Last commits:
a1b2c3d feat(payments): add retry logic with exponential backoff
e4f5g6h test(payments): add Vitest coverage on retry scenarios
i7j8k9l chore: update pnpm lockfile
Pipeline: running
✅ lint 30s
✅ typecheck 45s
⏳ test running...
⏸️ deploy waiting
URL: https://gitlab.com/org/my-app/-/pipelines?ref=feat/add-payment-retry
/ci:status
/ci:status 42 # MR or PR number 42
Target: $ARGUMENTS
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.
Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.
Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.
Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.
Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.
Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.