How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/zihad550/skills --skill work-shipBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Work ship
Take a work branch from "committed" to "in review". Run every command against the branch's worktree path. The reviewer is the one the user names in the arguments, or else the PR reviewer the repo's AGENTS.md names; with neither, ask. The issue always goes to the reviewer.
A review round is a run on an open PR that has a review requesting changes. In a review round, review is re-requested from the change requesters: every user whose latest review on the PR is REQUEST_CHANGES, read from tea api /repos/<owner>/<repo>/pulls/<pr>/reviews.
Steps
- Check the branch. Read the branch name, take the issue number from it (
jd-<n>-...orjd-<n>/...), and rungit log origin/development..HEAD --onelineandgit status --short. Look for an open PR whose head is this branch withtea pulls ls --state open --limit 200 --fields index,state,head,title -o simple. With an open PR, read its reviews and list the change requesters. Done when you hold the issue number, at least one commit ahead ofdevelopment, a clean working tree, the open PR number or none, and, for an open PR, whether this is a review round and who the change requesters are. Stop and report when the tree has uncommitted changes or the branch has no commits.
- Draft the PR. In a review round, compare the PR body with the commits pushed since the change request: when the body still describes the branch, keep it, say so in one line, and skip this step and step 4. Otherwise read
~/.agents/skills/work-pr-info/SKILL.mdand follow its steps 1 to 6; running inside this skill, the PR counts as ready for review unless the user said otherwise. Give the draft path and the title in one line, then stop until the user approves it or asks for changes. Done when the user has approved/tmp/draft-pr-<n>.mdas it stands.
- Push. Run the push as one plain command, with nothing chained before or after it:
git -C <path> push -u origin <branch>A chained push was denied in auto mode before any prompt appeared. Done when the remote branch matches HEAD.
- Open or update the PR. Write the draft's body, everything after its title and blank line, to a scratchpad file. With no open PR from step 1, create one:
tea pr create --repo <owner>/<repo> --base development --head <branch> --title "<title>" --description-file <body-file>With an open PR, run tea pr edit <pr> --repo <owner>/<repo> with the same --title and --description-file. The body is the draft exactly, with no attribution line added. Done when the PR shows the draft's title and body.
- Request review. Request the reviewer, or in a review round every change requester, through the reviewer field and leave the PR's assignees empty:
tea api -X POST /repos/<owner>/<repo>/pulls/<pr>/requested_reviewers -d '{"reviewers":["<login>", ...]}'Done when each requested user's latest entry in tea api /repos/<owner>/<repo>/pulls/<pr>/reviews is REQUEST_REVIEW and the PR has no assignees. Forgejo keeps a change requester under requested_reviewers after their review, so that field cannot tell a re-request happened (PR #939 listed @timos there before the re-request).
- Hand the issue over. Add the status label by name with
POST, which drops the oldstatus/*label and keeps every other label;PUTon that route replaces them all:
tea api -X POST /repos/<owner>/<repo>/issues/<n>/labels -d '{"labels":["status/ready for review"]}'
tea api -X PATCH /repos/<owner>/<repo>/issues/<n> -d '{"assignees":["<reviewer>"]}'
tea api -X PATCH /repos/<owner>/<repo>/issues/<n> -d '{"ref":"refs/heads/<branch>"}'The ref field is the issue sidebar's Branch/Tag picker; tea issue edit has no flag for it. Done when the issue carries status/ready for review, the reviewer as its only assignee, and ref set to the branch.
- Move the Linear task to
In Reviewby following~/.agents/skills/work-status/SKILL.md. Done when it prints the task's old and new status, or the task was alreadyIn Review.
- Report. In one list: the PR URL, who was requested for review (re-requested, in a review round), the issue's new label and assignee, and the Linear move. Then hand over work-pr-info's step 7 items, minus the jobs this skill already did. Done when every item work-pr-info kept out of the body is named with where it would live.

