Start issue
Update the base branch, create a feature branch for a ticket, and set the ticket in progress. Reads per-repo config from docs/agents/ (issue tracker, branching model), so it works in any repo and any language.From its SKILL.md
npx -y skills add TomWebwalker/skills --skill start-issueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.6 KB, as published. Nobody here has run it
Load config first. Read docs/agents/issue-tracker.md and docs/agents/vcs.md
from the repo. If they're missing, tell the user to run /setup-project-skills first
(or, if they decline, fall back to: tracker = none, base branch = the remote's
default branch, branch pattern = <id>). Use config values below instead of any
hardcoded names.
Steps
- Parse the ticket id from
$ARGUMENTSusingissue-tracker.md#ticket_id_pattern. If no ticket is given and tracker is notnone, ask for one; if tracker isnone, ask for a short kebab-case slug to name the branch. - If tracker is not
none, fetch the ticket perissue-tracker.mdto confirm it exists and read its title. - Check for uncommitted changes. If the working tree is dirty, stop and ask what to do (stash, commit, or abort) rather than switching branches under the user.
- Check out
vcs.md#base_branchand pull latest. - Create the branch from
vcs.md#branch_pattern, substituting<id>with the ticket id or slug. If the branch already exists, check it out instead of failing, and say so. - If tracker is not
noneandstatuses.in_progressis set, move the ticket to that status using the method described inissue-tracker.md. - Confirm the branch is ready and (if applicable) the ticket was updated.