// Stage, commit, and push changes to the remote repository with a well-formed commit message.
Perform a structured code review of staged or recently changed Warpine source files, covering correctness, security, test coverage, clean-room compliance, and documentation hygiene.
Audit and update all project documentation to stay in sync with the current development status.
Manage the full software release process, including version bumps, changelogs, Git tags, and GitHub releases.
Perform project-wide security audits focused on KVM hypervisor escape, guest memory safety, and dependency vulnerabilities.
| name | commit-and-push |
| description | Stage, commit, and push changes to the remote repository with a well-formed commit message. |
When committing and pushing changes, always follow these steps:
Run tests and lint with cargo test and cargo clippy -- -D warnings. Ensure all tests pass and there are zero clippy warnings. If either fails, stop and report the failures to the user โ do not proceed with staging or committing until both are clean.
Stage all relevant changes with git add. Be deliberate โ stage only files related to the current topic. Never blindly stage everything with git add -A if unrelated changes are present.
Commit with a clear, concise message following the Conventional Commits standard (e.g., feat(loader): implement DosSetFilePtr). The message should explain why the change was made, not just what changed. Append a co-author trailer:
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Pass the full message via a heredoc to preserve formatting. Never use --no-verify to skip hooks unless the user explicitly requests it.
Push the committed changes to the current branch on the remote repository.
Verify that the push succeeded and the remote is in sync with the local branch.