Push the current Git branch and get a link to its GitLab CI or GitHub Actions runs. The workflow checks for uncommitted changes and blocks direct pushes to main, master, and production before proceeding.
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions)
Review the instructions the agent will receive before you install.
Pushes the current branch and returns the pipeline tracking link.
BRANCH=$(git branch --show-current)
# 1. Safety checks
if echo "$BRANCH" | grep -qE "^(main|master|production)$"; then
echo "❌ Direct push to $BRANCH is not allowed. Create a feature/fix branch."
exit 1
fi
# 2. Check for uncommitted changes
UNCOMMITTED=$(git status --porcelain | wc -l | tr -d ' ')
if [ "$UNCOMMITTED" -gt 0 ]; then
echo "⚠️ $UNCOMMITTED uncommitted file(s):"
git status --short
echo ""
echo "Commit first with /commit or git add + git commit"
exit 0
fi
# 3. Push
echo "Pushing → origin/$BRANCH"
git push origin "$BRANCH" 2>&1
REMOTE=$(git remote get-url origin 2>/dev/null || echo "")
WEB_URL=$(echo "$REMOTE" | sed 's/git@gitlab\.com:/https:\/\/gitlab.com\//' | sed 's/\.git$//')
echo ""
echo "✅ Push OK"
echo " Pipeline: $WEB_URL/-/pipelines?ref=$BRANCH"
# Live status via glab (if installed)
if command -v glab &>/dev/null; then
sleep 3
glab ci status --branch "$BRANCH" 2>/dev/null || true
fi
REMOTE=$(git remote get-url origin 2>/dev/null || echo "")
WEB_URL=$(echo "$REMOTE" | sed 's/git@github\.com:/https:\/\/github.com\//' | sed 's/\.git$//')
echo ""
echo "✅ Push OK"
echo " Actions: $WEB_URL/actions?query=branch%3A$BRANCH"
# Live status via gh (if installed)
if command -v gh &>/dev/null; then
sleep 5
gh run list --branch "$BRANCH" --limit 3 2>/dev/null || true
fi
Pushing → origin/feat/add-payment-retry
Enumerating objects: 12, done.
...
✅ Push OK
Pipeline: https://gitlab.com/org/my-app/-/pipelines?ref=feat/add-payment-retry
Pipeline status (after 3s):
⏳ lint running
⏸️ test waiting
⏸️ deploy waiting
/ci:pipeline
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.