Agent skill
submit
Use after review passes — creates PR, waits for CI, and merges only after CI is green
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/submit-dodi-hq-dodi-skills
SKILL.md
Submit
Create a PR, wait for CI to pass, then merge.
Process
-
Pre-flight:
- Verify you're on a feature branch (not main/master)
- Check for uncommitted changes — commit or warn
- Ensure branch is pushed to remote
- Run
/quality-gate— this is mandatory. Invoke the quality-gate skill to run compliance checks, create tests, and run the test suite. Do NOT skip this step.
-
Create PR:
bashgit push -u origin <branch> gh pr create --title "<title>" --body "$(cat <<'EOF' ## Summary <2-3 bullets> ## Test Plan - [ ] <verification steps> 🤖 Generated with [Claude Code](https://claude.com/claude-code) EOF )" -
Enable auto-merge: GitHub will automatically squash-merge once CI passes and delete the remote branch.
bashgh pr merge <pr-number> --squash --delete-branch --auto- Report the PR URL to the user
- Update ticket status if tracker tools available
- Do NOT poll or wait — auto-merge handles it asynchronously
Note: Local worktree and branch cleanup happens automatically at the next
pickup.
Key Rules
- Never force-merge or use --admin without explicit user approval
- Always squash-merge (clean history)
- Always use --auto — let GitHub merge when CI passes, don't block the conversation
- Delete branch after merge (keep repo clean)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?