submit-issue-work - SKILL.md Agent Skill

name: submit-issue-work description: Submit completed work for a OneDev issue. Use when the user asks to submit, complete, or finish issue work.

Submit work on a OneDev issue

Submit code changes and/or saved comments for an issue.

Prerequisites

tod is installed and configured.
The current repository belongs to the issue's project.

Session handoff

This workflow pairs with work-on-issue. At the start, recover <saved-issue-comments> from the same chat session:

From a prior work-on-issue run — use the exact drafted comment text presented or amended earlier in this session.
From the user's submit prompt — if the user supplies or revises comment text when asking to submit, treat that as <saved-issue-comments>.
Otherwise — <saved-issue-comments> is empty.

<saved-issue-comments> is session state, not a file on disk and not comments already on OneDev. Step 7 posts these deferred drafts.

Stop on error

Run the workflow sequentially. On any command failure, missing required output, failed precondition, or declined confirmation, stop immediately, report the command and error, and wait for the user. Do not continue, retry silently, amend, or force-push.

If not submitting

If you decide not to run submission for any reason, make sure to create an issue comment explaining why the work was not submitted:

tod issue add-comment <issue-reference> "<reason>"

Workflow

Given an optional <issue-reference> (e.g. 123, #123, myproject#123, or PROJ-123):

Resolve the issue reference. If the user prompt or session context already provides <issue-reference>, use it. Otherwise derive it from the working directory:
```
tod issue current-reference
```
Save non-empty output as <issue-reference>. If the output is empty, stop and report that the issue reference could not be derived.
Check whether code can be submitted.
```
git symbolic-ref --short HEAD 2>/dev/null
```
Save successful output as <current-branch>. If there is no branch, skip to step 7 to apply saved issue comments, and continue with rest steps.
Verify the current branch.
```
tod issue get <issue-reference>
tod project current
tod remote
git fetch <remote> <issue-branch>
git rev-parse --abbrev-ref <current-branch>@{upstream}
```
Save the issue detail as <issue> and get <issue-branch> from that response. If the branch is missing from the issue detail, report that the issue does not have a branch on the server yet and stop. Save the other outputs as <current-project>, <remote>, and <upstream>. Verify that <current-project> equals the issue project, <current-branch> equals <issue-branch>, and <upstream> equals <remote>/<issue-branch>. If any check fails, report the mismatch and stop.
Find the PR, or plan to create one.
```
tod pr list --query 'includes issue "<issue-reference>" and open'
```
- One match: Read it and verify its source project and branch match the verified issue project and branch:
```
tod pr get <pr-reference>
```
  Record the PR reference, URL, source, and target values.
- No matches: Plan to create a PR. Use user-provided target project and target branch values first. For any missing target value, use the corresponding default from the issue detail already read in step 3. If a required target value is still missing, report that work is not submitted because that value is missing, and stop. Otherwise record the planned PR target values.
- Multiple matches: Ask the user which PR to use, then stop.
Commit code changes when the working copy is dirty.
```
git status --porcelain
```
If the output is empty, skip this step. Otherwise inspect the diff and compose the message here (do not use the generate-commit-message skill) from:
```
tod get-commit-message-requirement
tod pr get-commit-message-requirement --target-project <target-project> --target-branch <target-branch>
```
Pass the existing or planned PR target values from step 4. Satisfy all non-empty requirements and ask the user to confirm the full message before running:
```
git add -A
git commit -m "<subject>" -m "<body>"
git status --porcelain
```
The final status must be clean.
Push outstanding commits and create a PR when needed.
```
git log --reverse --pretty=format:'%h %s%n%b%n---' <remote>/<issue-branch>..HEAD
```
Save the output as <commits-to-push>. If it is empty, skip the push and PR creation and continue to deferred comments or state changes. Otherwise:
```
git push <remote> <issue-branch>
```
- For an existing PR, the push updated it. Report its reference and URL.
- If no PR was found in step 4, read the new PR requirements using the same planned flags:
```
tod pr get-title-and-description-requirement --target-project <target-project> --target-branch <target-branch>
```
  Compose a concise title and description from the captured commits, validate them, and obtain confirmation before:
```
tod pr create "<title>" --description "<description>" --target-project <target-project> --target-branch <target-branch>
```
  Pass the resolved target project and target branch values and report the returned PR reference and URL.
  
  Note that if you want to mention the pull request in comment, make sure to use form pr #<pr number>.
Apply deferred OneDev changes. Post <saved-issue-comments> from Session handoff, whether or not this workflow submitted code. If code submission started and then failed, do not post saved comments.
- If <saved-issue-comments> is non-empty, post every comment — do not skip because a PR description already covers the same ground.
- If <saved-issue-comments> is empty and no code was submitted, report that there is nothing to submit.
For each comment in <saved-issue-comments>, run:
```
tod issue add-comment <issue-reference> "<comment>"
```
Restore the previous branch and clean up the current branch if applicable.
```
git rev-parse --abbrev-ref @{-1} 2>/dev/null
```
Save successful output as <previous-branch>. If the command fails or returns an empty value, stop.
- If <current-branch> was not recorded in step 2:
```
git checkout <previous-branch>
```
- If <current-branch> differs from <previous-branch>:
```
git checkout <previous-branch>
git branch -d <current-branch>
```
- If <current-branch> equals <previous-branch>, do nothing.