start-work
/start-work
Przygotowuje pracę nad zgłoszeniem: znajduje lub zakłada je, pisze i sprawdza plan, a potem tworzy gałąź.
- Autor
- serionist ↗
- Repozytorium
- claude-sticky ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Przygotowuje pracę nad zgłoszeniem: znajduje lub zakłada je, pisze i sprawdza plan, a potem tworzy gałąź.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use when someone wants to work on something in claude-sticky ("let's do #12", "pick up the pane bug", "add a kind of item", "fix Y"), before any code or docs change. Finds or creates the issue, reads the code and the APIs it touches, decides whether it needs a plan, writes the plan and reviews it with review-plan until it is approved, then starts the branch from origin/main with the plan as its first commit.
Jak działa
- Steps
- Done means
- Never
Podgląd SKILL.md
---
name: start-work
description: >-
Use when someone wants to work on something in claude-sticky ("let's do #12", "pick up the pane bug",
"add a kind of item", "fix Y"), before any code or docs change. Finds or creates the issue, reads the code and the
APIs it touches, decides whether it needs a plan, writes the plan and reviews it with review-plan until it is
approved, then starts the branch from origin/main with the plan as its first commit.
---
# Start a change
Every change reaches `main` through a PR (`AGENTS.md`, How a change lands). This skill gets a change to where code can
start: an issue, a plan when it needs one, the plan approved, and a branch. `finish-work` closes it.
## Steps
1. **Find the issue.**
- A number: `gh issue view <n> --comments`, read in full. Closed? Ask before going on.
- A sentence: look for an open one first, `gh issue list --search "<words>"`. None fits: write the body to
`.local/issue-body.md` (what and why, no tool attribution) and run
`gh issue create --title "<title>" --body-file .local/issue-body.md`. A typo or comment fix needs no issue.
2. **Read before planning,** never from memory:
- the code of every file the change touches, and its tests: `plugin/hooks/register.tsx` for the hooks, the text
Claude reads and the drawing, `plugin/hooks/register.test.tsx` for its tests, `plugin/types/index.d.ts` for the
board and the state;
- `docs/design.md`, the READMEs and `REVIEW.md`;
- every hooks API it will call, in `plugin/.claude-plugin/types/claude-code/index.d.ts` (load the mod once with
`claude --plugin-dir plugin` if it is not there), and anything outside Claude Code (a terminal's notification
support, a model's behaviour) through Context7 or the vendor's docs (`AGENTS.md`, Look up APIs before coding
against them).
3. **Decide whether it needs a plan,** by the rule in `docs/plans/README.md`. Unsure: ask, and recommend one for
anything that touches a one-way door, the text Claude reads, or the saved board's fields.
4. **Write the plan** at `docs/plans/<today>-<slug>.md` from the template in `docs/plans/README.md`, with `issue` set.
Fill every section; "none" is an answer, a blank is not. A one-way door it changes is named under Compatibility.
5. **Review it** with `review-plan` until its verdict is `approved`.
6. **Get it approved** by the maintainer: give the plan's path and the review's verdict, and ask. No code before the
yes. Then set `status: approved`, `approved_by` (their GitHub login) and `approved_at` in the frontmatter.
- Someone outside the maintainers: do steps 7 and 8 first, push the branch to your fork, and open a draft PR titled
`Plan: <title>` that links the issue. The maintainer approves it there, and the code lands on the same branch.
7. **Start the branch** `<n>-<slug>` from `origin/main`, after `git fetch origin`. Ask where, as one question with a
recommendation:
- a new branch here, `git switch -c <n>-<slug> origin/main`, when the checkout is clean and nothing else runs in
it;
- a new worktree, `git worktree add .claude/worktrees/<n>-<slug> -b <n>-<slug> origin/main`, when other work is
in flight; then move the session there, and run `npm ci` in it.
- `post-checkout:` lines name AI setup files that changed on the way: re-read the ones you already read, this
skill among them.
8. **Commit the plan** as the branch's first commit: subject `Plan: <title>`, body `Refs #<n>`.
9. **Ask how to build:** directly in this session, or in forked agents for independent steps, each brief naming the
plan's path, its step and the files it may touch. This session stays the plan's anchor either way.
## Done means
- The issue exists, unless the change is a typo or comment fix.
- A change that needs a plan has one, reviewed, approved, and committed first on its branch.
- The branch exists from `origin/main`, and how to build is chosen.
## Never
- Write code before the plan is approved, or on `main`.
- Plan from memory of the code or of an API instead of reading it.
- Keep a plan only in the session, an issue comment or a PR body: the plan is a file.
- Post an issue or a comment with tool attribution in it.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · serionist/claude-sticky | 90 | MIT |
| kmedi355/team-git-skills | 100 | MIT |
| code-yeongyu/lazyclaudecode | 100 | MIT |
| dmzoneill/skills | 90 | Apache-2.0 |
| serionist/claude-session-restore | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 1eae7a516842 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100start-issue
Przygotowuje środowisko do pracy nad zgłoszeniem GitHub: tworzy gałąź z origin/development, przełącza persistence.xml na lokalne ustawienia JNDI, przypisuje issue i prowadzi przez konfigurację tablicy projektu. - 100pick-plan
Wybiera następny plan do realizacji z PLAN.md, uwzględniając otwarte pull requesty, gałęzie i zależności, po czym tworzy gałąź, szkic PR i uruchamia agenta implementacji. - 100start
Rozpoczyna pracę nad zgłoszeniem Linear: sprawdza blokery, przypisuje zadanie, przygotowuje gałąź i planuje implementację. - 90start-issue
Czyta zgłoszenie z GitHub Devcules albo wolny opis zadania, sprawdza zależności i tworzy gałąź z aktualnego main. - 100start
Zaczyna pracę w repozytorium ai-agent-skills: dla istniejącego issue pobiera je i tworzy gałąź, dla nowego klasyfikuje, spisuje wymaganie z szablonu, zakłada issue i tworzy gałąź. - 100git-branch-create
Tworzy i przełącza na nową gałąź Git według konwencji nazewnictwa, gdy zaczyna się wyodrębniona porcja pracy.