| name | validate-update-push |
| description | Complete workflow to validate build, update documentation, update progress, and push changes. Use when finalizing work, before ending a session, or when the user says "finalize", "wrap up", or "ship it". |
| allowed-tools | Bash, Read, Write, Edit, Glob, Skill |
| user-invocable | true |
Validate, Update & Push
Sequential workflow to validate, document, and push changes.
Step 1: Validate
Run /validate to check available validations:
- Lint (if configured)
- Build (if configured)
- Tests (if configured)
The validate skill automatically detects which scripts are available in package.json and skips those that aren't configured.
If validation fails:
- Report the error clearly
- Ask: "Validation failed. Do you want me to fix this issue?"
- Wait for user response
- If user agrees, fix and re-run validation
- If user declines, stop the workflow
Step 2: Update Documentation
Run /update-docs to update:
CLAUDE.md (if meaningful changes exist)
memory-bank/ files (except brainstorm.md)
If no updates needed, continue.
Step 3: Update Progress (Conditional)
Check if applicable:
- Search for implementation plan (in priority order):
memory-bank/plan.md or memory-bank/*-implementation-plan.md
*-implementation-plan.md or implementation-plan.md (project root)
docs/*-implementation-plan.md
- If NO plan exists, skip this step
If plan exists:
- Determine if work relates to a task in the plan
- If yes, run
/update-progress
- If unrelated, skip
Step 4: Git Add, Commit & Push
Run /git-add-commit-push to:
- Stage all changes
- Create commit with appropriate message
- Push to current branch
Error Handling
At any step, if something unexpected happens:
- Explain what went wrong
- Ask the user how to proceed
- Never force through errors silently
Output
## Summary
- Validation: [Passed / Fixed N issues]
- Documentation: [Updated X files / No updates needed]
- Progress: [Updated / Skipped (no plan) / Skipped (unrelated work)]
- Git: [Committed and pushed / Skipped]