work-tracking
/work-tracking
Łączy zadania z gałęzią, commitami i pull requestami w Jira, Azure Boards lub GitHub Issues oraz sprawdza wyniki CI.
- Autor
- catafeidi ↗
- Repozytorium
- abap-ai-kit ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 29.10.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 29.10.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
Łączy zadania z gałęzią, commitami i pull requestami w Jira, Azure Boards lub GitHub Issues oraz sprawdza wyniki CI.
Oryginalny opis (EN)
Use when development or investigation work touches the project's tracker, code host or CI - finding or creating the ticket for a task, linking branch / commits / pull request to it, recording open points as tickets, updating or closing tickets, checking pipeline results. Works with Jira, Azure Boards or GitHub Issues and GitHub, Azure Repos or GitLab, as declared in the project's integrations.json.
Jak działa
- At the start of a task
- While working
- At the end
- Never
Podgląd SKILL.md
--- name: work-tracking description: Use when development or investigation work touches the project's tracker, code host or CI - finding or creating the ticket for a task, linking branch / commits / pull request to it, recording open points as tickets, updating or closing tickets, checking pipeline results. Works with Jira, Azure Boards or GitHub Issues and GitHub, Azure Repos or GitLab, as declared in the project's integrations.json. --- # Work tracking Rules: kit `rules/work-tracking.md`. Adapters and commands: kit `guidelines/integrations.md`. Configuration: `<project>/integrations.json` (`tracker`, `code`, `ci`). If `tracker.preferSkill` names a project skill (team templates), use that skill for creating and editing tickets and this one only for the flow around it. ## At the start of a task 1. Read `integrations.json`. No `tracker` block: skip the ticket steps and say so once. 2. Find the ticket: by key if the user gave one, else search the project for the topic. None fits: draft one (type by the rules, defaults from the config) and ask before creating it. 3. Read the ticket: description, acceptance criteria, links, latest comments. State in one line what it asks for and anything that conflicts with the request. 4. Code host: check the account (`code.account`), create the branch with the ticket key (`code.rules.branch`). ## While working - A new open point, risk or follow-up: draft a linked ticket (Spike / Bug / Story) and list it for the user; create after confirmation. Record the key in the project notes. - Commits and pull requests carry the key (`code.rules.prTitle`). Follow project rules that forbid hand-made pull requests for some code (e.g. ABAP released through SAP). ## At the end 1. CI: read the pipeline result of the change (`gh pr checks` / `gh run view --log-failed`, Azure Pipelines runs); a red result is reported, not hidden. 2. Compare the ticket with what was built: done / partly / needs change / decision needed. 3. Draft the ticket update (comment, fields, transition with the evidence the acceptance criteria ask for) and send it only after the user agrees. 4. Write the ticket state into the topic's notes (Now / Next). ## Never - Invent a ticket key, field ID or transition ID. Look it up, then propose adding it to `integrations.json`. - Write to the tracker on a day or in a way the project rules forbid (`rules.weekdaysOnly`).
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · catafeidi/abap-ai-kit | 90 | MIT |
| queen-of-code/ai-dlc | 100 | MIT |
| slogsdon/skills-workflows | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 3fddbdb9089b (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
- 90ticket-sync
Wysyła zadania do systemu zgłoszeń zespołu, np. GitHub Issues, Jira lub Azure DevOps, i może je także pobrać z powrotem. - 100work-item-linking
Łączy commity i pull requesty z elementami Azure DevOps Boards oraz wykonuje zapytania WIQL z wiersza poleceń. - 90using-tracker
Obsługuje zgłoszenia, zadania i backlog w Linear, Jira, GitHub Issues lub lokalnych plikach, w tym tworzenie i aktualizację. - 96jira-tickets
Tworzy, aktualizuje, sortuje i usuwa zgłoszenia w Jira przez polecenia CLI jira. - 100ticket-writing
Pisze zgłoszenia w Jira, GitLab i GitHub tak, by czytelnik szybko ocenił sprawę i zrozumiał powód zmiany. - 90find-information
Szuka faktów w źródłach projektu, czyli notatkach, wiki, repozytoriach i trackerze, i podaje źródło każdego faktu.