ddev-cleanup

ddev-cleanup

Role

Perform a complete, clean shutdown of the current Grok Build + ddev project session. Enforce no project drift, verify GitHub/repo health, deliver via feature branches (never leave the workspace on master or develop), and ensure seamless resumption the next day.

Activation

Use when the user says "end of day", "shutdown for today", "clean stop", "daily cleanup", "stop work", "push and shutdown".

Branch policy (orchestrator template)

Promotion flow: feature/* → PR → develop → PR → master (branch-promotion-prs.yml).

Procedure (run in order)

1. Repository status check (mandatory — /github-expert lite)

Activate /github-expert or run these checks from project root:

git fetch origin --prune
git branch --show-current
git status -sb
git rev-list --left-right --count origin/develop...develop 2>/dev/null || true
git rev-list --left-right --count origin/master...master 2>/dev/null || true
gh pr list --limit 10
gh pr list --state merged --limit 5

Report an EOD repo status table:

Cache findings in session summary; update docs/github/repo-health.md when drift or recurring issues appear.

2. Enforce no project drift

• Activate .github/skills/project-drift-guardian/SKILL.md and /branch-context-agent.
• Align with active TODO and branch scope.
• Resolve drift before commit/push.

3. Branch gate before commit

If current branch is master or develop:

git checkout develop
git pull origin develop
git checkout -b feature/<slug>-$(date +%Y-%m-%d)

• <slug>: short kebab from TODO objective or user hint (e.g. loop-hardening, work).
• Move any uncommitted work onto this branch before staging.

If already on feature/* with aligned scope, stay.

4. Stop ddev environment

• Run ddev stop (or ddev poweroff if no other projects active) when .ddev/ exists.
• Confirm with ddev list or ddev describe.
• Template repos without .ddev/: skip and note N/A.

5. Update Grok Build artifacts

• Refresh project cache if applicable.
• Run python3 scripts/sync_grok_to_github_claude.py when .grok/ skills or prompts changed.
• Update active TODO (today closed, tomorrow opened via /todo-specialist-agent when chained).
• Run bash scripts.github/skills/chain/SKILL.md-audit.sh when chains/registry.yaml changed.

6. Git cleanup and push

git status
git add <relevant files>
git commit -m "End of day cleanup: <summary>. No project drift confirmed."
git push -u origin "$(git branch --show-current)"

• Open PR to develop when branch protection blocks direct push.
• Never push EOD commits to master or develop.

7. Reposition for tomorrow (mandatory if on master or develop)

After push (or when working tree is clean on a promotion branch):

git checkout develop
git pull origin develop
git checkout -b feature/<slug>-$(date -d tomorrow +%Y-%m-%d 2>/dev/null || date -v+1d +%Y-%m-%d)

• Use tomorrow's date in the branch name when creating the next-day branch.
• Leave the workspace on this feature branch — not on master.
• Empty branch: no push required until first commit tomorrow.

8. Final verification

• Confirm last push succeeded (if any).
• Confirm current branch is feature/*.
• Suggest tomorrow: ddev start (if applicable), .github/skills/chain/SKILL.md session-start (offers resume to latest remote branch worked on), active TODO/YYYY-MM-DD_TODO.md.

Idempotency

• Check before destructive actions (git branch -D, force push).
• If already on a suitable feature/* with clean tree, skip step 7.
• Safe to re-run; repo status step always runs.

Chained use

Part of eod-shutdown chain (todo-specialist → readme-specialist → ddev-cleanup). Repo status + branch reposition are owned by this skill's steps 1, 3, and 7.

Run commands via bash tool. Always work in project root. Log each step.