start-issue
/start-issue
Start work on a Devcules GitHub issue or an ad-hoc task. Reads the issue (or takes free text), checks dependencies, and creates a users/kiran/<slug> branch from an updated main. Use when asked to start, pick up or work on an issue number, or to start an ad-hoc branch from a text description.
- Author
- devcules ↗
- Repository
- devcules ↗
- Licence
- Apache-2.0
- Last repository change
- 04.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Start work on a Devcules GitHub issue or an ad-hoc task. Reads the issue (or takes free text), checks dependencies, and creates a users/kiran/<slug> branch from an updated main. Use when asked to start, pick up or work on an issue number, or to start an ad-hoc branch from a text description.
Original author description
Start work on a Devcules GitHub issue or an ad-hoc task. Reads the issue (or takes free text), checks dependencies, and creates a users/kiran/<slug> branch from an updated main. Use when asked to start, pick up or work on an issue number, or to start an ad-hoc branch from a text description.
How it works
- Issue path (a number was given)
- Ad-hoc path (free text, no issue number)
- Updating main and branching
SKILL.md preview
--- name: start-issue description: Start work on a Devcules GitHub issue or an ad-hoc task. Reads the issue (or takes free text), checks dependencies, and creates a users/kiran/<slug> branch from an updated main. Use when asked to start, pick up or work on an issue number, or to start an ad-hoc branch from a text description. --- # Start an issue Input: an issue number (e.g. `/start-issue 3`) or free text describing ad-hoc work (e.g. `/start-issue add agent skills`). ## Issue path (a number was given) 1. Run `gh issue view <number>`. Note the module id from the title (e.g. `M0.3`), the scope, the "Depends on" line and the test gate. 2. Check the dependency is done: the previous module's issue must be closed (`gh issue view <previous> --json state -q .state` shows `CLOSED`). If it isn't, stop and say so. Skip this when the issue says "Depends on: none". 3. Check the working tree is clean (`git status --porcelain` prints nothing). If it isn't, stop and list the changes. Never stash or discard them yourself. 4. Update main, then branch from it (see below). Make `<module>` the lowercase module id (`m0.3`) and `<slug>` two to four lowercase words from the title, joined by hyphens. 5. Check `git config user.email` is not a work address. 6. Reply with: the branch name, a three-line summary of the scope, the test gate as a checklist, and your plan in at most five steps. Then wait for the go-ahead before writing code. ## Ad-hoc path (free text, no issue number) 1. Check the working tree is clean (`git status --porcelain` prints nothing). If it isn't, stop and list the changes. Never stash or discard them yourself. 2. Update main, then branch from it (see below). Make the slug two to four lowercase words from the given text, joined by hyphens (`users/kiran/<slug>`). 3. Check `git config user.email` is not a work address. 4. Reply with: the branch name and a three-line summary of the work. Then wait for the go-ahead before writing code. ## Updating main and branching Unless the user names a different base: run `git switch main`, then `git pull --ff-only` to update it. If the update fails (e.g. local main has diverged), stop and say so. Then run `git switch -c users/kiran/<name> main`. If the branch already exists, switch to it instead, then run `git log origin/main..HEAD --oneline` to see what's on it.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · devcules/devcules | 90 | Apache-2.0 |
| hmislk/hmis | 100 | GPL-3.0 |
| gopherguides/gopher-ai | 90 | MIT |
| sejas/ai-code-skills | 90 | MIT |
Database snapshot: 13.11.2026 · package version 7cada25d72a3 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 86ship-pr
Finish a Devcules module. Runs the checks, commits with a DCO sign-off on the users/kiran/ branch, pushes, and opens a PR that closes the issue. Never merges. Use when the work for the current issue is done and should go up for review. - 100pick-up-issue
This skill should be used when the user asks to "pick up an issue", "work on issue #X", "claim issue", "start working on issue", "take this issue", "I'll work on this", or needs to take ownership of a GitHub issue before starting work. - 100start
Begins a new piece of work in the ai-agent-skills repository. Two modes: EXISTING ISSUE (user provides a GitHub issue number or URL — fetches it, cuts the correct branch) and NEW ISSUE (user describes what needs doing — classifies as feature or bug, drafts a structured… - 100implement-issue
Read a GitHub issue, create a branch, implement the solution, and open a PR. Use when given an issue number to implement. - 100implement-issue
Implement a julianpalomo.dev GitHub issue end to end. Reads it with gh, creates its branch, posts the plan on the issue and waits for an OK, implements, runs /handoff and /ship-pr, then acts on the PR's review. Use when asked to implement, build or work on an issue by number. - 100git-branch-create
Create a new git branch using a conventional naming scheme. Use when the user asks to create a branch, start a new branch, /git-branch-create, or signals they are beginning a discrete piece of work - "start work on X", "spin up a branch for Y", "let's start Z". Boundary: a…