f5xc-cloudstatus-mcp: Instructions file for Claude Code

Claude Code Project Instructions

Repository Workflow

This repo enforces a strict governance workflow. DO NOT STOP after creating a PR — the task is not complete until the PR is merged, all post-merge workflows succeed, and local branches are cleaned.

Making Changes (Steps 1-5)

1. Create a GitHub issue before making any changes
2. Create a feature branch from main — never commit to main directly
3. Commit changes with conventional format (feat:, fix:, docs:) and push to remote
4. Open a PR that links to the issue using Closes #N — fill out the PR template completely
5. Fix any CI failures — monitor checks with gh pr checks <NUMBER>, fix locally, push to trigger re-runs

Waiting for Auto-Merge (Step 6)

1. Wait for auto-merge — PRs merge automatically (squash) once all CI checks pass. Poll until the PR state is MERGED:

   gh pr view <NUMBER> --json state --jq '.state'
   

   If the PR is not merging, check for issues:

   gh pr view <NUMBER> --json mergeable,mergeStateStatus
   

Post-Merge Monitoring (Steps 7-8)

1. Monitor post-merge workflows — merging to main triggers additional workflows (docs builds, governance sync, etc.). Discover and watch them:

   git checkout main && git pull origin main
   MERGE_SHA=$(git rev-parse HEAD)
   sleep 10
   gh run list --branch main --commit $MERGE_SHA
   gh run watch <RUN-ID> --exit-status
   

2. Iterate on failures — if any workflow fails:

   • View logs: gh run view <RUN-ID> --log-failed
   • Analyze the root cause
   • Fix the code locally
   • Create a new issue, branch, and PR with the fix
   • Return to Step 5 and repeat until all workflows pass
   • For pre-existing failures unrelated to your changes: create a GitHub issue (per CI Monitoring rules below) and continue

Cleanup (Steps 9-10)

1. Clean up branches — only after all workflows succeed. Delete your feature branch and any other stale local branches already merged to main: