tod

Create or edit a OneDev CI/CD spec (`.onedev-buildspec.yml`) using the `tod` CLI to fetch the schema and validate the result. Use when the user asks to set up CI/CD, configure build spec, or otherwise author `.onedev-buildspec.yml`.

Generate a git commit message for the current change in a OneDev project that conforms to the project's commit-message requirement (and, when the commit will be part of a pull request, the pull request commit-message requirement) and includes a meaningful body or footer. Use when the user asks to write, draft, generate, or compose a commit message.

Investigate why a OneDev build failed or misbehaved by reading its metadata, log, referenced files, and recent changes via the `tod` CLI. Use when the user asks to debug, diagnose, or triage a failing or suspicious OneDev build.

Perform a structured code review of a OneDev pull request via the `tod` CLI, examining metadata, patch, referenced files, and prior code comments, then leaving line-anchored code comments, replies, resolutions, and an overall approve/request-changes/comment decision. Use when the user asks to review, approve, request changes on, or comment on a OneDev pull request.

Submit completed work on a OneDev issue via the `tod` CLI — confirm the issue branch exists on the server, verify the local checkout is on it, commit any pending changes (using the `generate-commit-message` skill), push to the matching remote branch, and open a pull request whose title and description summarize the commits added on the issue branch. Use when the user asks to submit, complete, or finish work on a OneDev issue (e.g. "submit work 123", "complete work on PROJ-7", "finish issue myproject#42").

Submit completed work on a OneDev pull request via the `tod` CLI — verify the checkout is on the PR's source branch in the source project, commit any pending changes (using the `generate-commit-message` skill), push to the matching remote branch so the existing pull request picks up the new commits, then post any deferred PR/issue/code-comment replies from work-on-pull-request. Use when the user asks to submit, push, or finish work on a pull request (e.g. "submit PR work", "push my PR fixes", "submit work on PR 42").

Drive OneDev (issues, pull requests, builds) through the `tod` CLI. Use whenever the user asks to create, edit, query, change state, comment on, review, checkout, run CI/CD job for, get commit message requirement, or otherwise interact with anything in OneDev.

Set up the local checkout to work on a OneDev issue via the `tod` CLI — check for an existing open pull request linked to the issue (and delegate to work-on-pull-request when there is exactly one), otherwise create the issue branch on the server, switch to it locally with the right remote tracking, read the issue context, and implement the work. Use when the user asks to start, pick up, begin, or work on a OneDev issue.

Set up the local checkout to address concerns on a OneDev pull request via the `tod` CLI — verify the working directory is the PR's source project, check out the PR branch, inspect feedback (PR comments, code comments, linked issue comments, failed builds, or the user's prompt), then fix code locally and draft or post OneDev replies. Replies that claim a code fix must not be posted until after `submit-pull-request-work` pushes. Use when the user asks to work on, address, fix, or follow up on a pull request (e.g. review feedback, failing CI, or requested changes).