/goalcihigh riskbeginnersafety C · 55

/goal edit get CI green for PR 87469…

Community goal loop for ci, sourced from github. Verified exit condition, evaluator-gated.

prompt
→ Claude
/goal /goal edit get CI green for PR 87469, push the fix, and update docs
claude-code

Source: promisingcoder

More ci loops

--- name: gsd:ship description: Create PR, run review…

/ralphnew

Community ralph loop for ci, sourced from github. Verified exit condition, evaluator-gated.

prompt
→ Claude
--- name: gsd:ship description: Create PR, run review, and prepare for merge after verification passes argument-hint: "[phase number or milestone, e.g., '4' or 'v1.0']" allowed-tools: - Read - Bash - Grep - Glob - Write - AskUserQuestion --- <objective> Bridge local completion → merged PR. After /gsd:verify-work passes, ship the work: push branch, create PR with auto-generated body, optionally trigger review, and track the merge. Closes the plan → execute → verify → ship loop. </objective> <execution context> @C:/Users/Paulo/OneDrive/Área de Trabalho/Projetos Vibe Coding/kakashi-flix-aiox/kakashi-flix/.claude/get-shit-done/workflows/ship.md </execution context> Execute the ship workflow from @C:/Users/Paulo/OneDrive/Área de Trabalho/Projetos Vibe Coding/kakashi-flix-aiox/kakashi-flix/.claude/get-shit-done/workflows/ship.md end-to-end
cihigh risk

--- description: Create pull request with summary allowed-tools…

/ralphnew

Community ralph loop for ci, sourced from github. Verified exit condition, evaluator-gated.

prompt
→ Claude
--- description: Create pull request with summary allowed-tools: Bash(git: ), Bash(gh: ) --- Create a pull request for the current branch following PR standards defined in .claude/rules/pr-standards.md . ## Steps 1. Check state bash git status git log main..HEAD --oneline git diff main..HEAD --stat 2. Ensure pushed bash git push -u origin HEAD 3. Analyze changes thoroughly - Review all commits and actual code changes since branching from main - Identify PR type: feature, fix, refactor, docs, chore - Determine the user story: who benefits and why - Check for breaking changes or migration needs - Note any acceptance criteria that should be verified 4. Create PR using appropriate template For Feature PRs (full template): bash gh pr create --title "feat(scope): description" --body "$(cat <<'EOF' ## User Story As a [type of user], I want [goal/desire], So that [benefit/value]. ## Summary Brief description of what this PR accomplishes and why. ## Changes - Change 1: description - Change 2: description ## Acceptance Criteria - [ ] Criterion 1: sp
cihigh risk

Fix CI, ship the PR

/loopnew

Check your PR's CI status and fix failures until the build passes.

prompt
→ Claude
/loop 5m check my PR and fix CI , /schedule |
cimedium risk