perform-task
/perform-task
Wdraża jedno zadanie z listy zadań, sprawdza je, testuje i zapisuje w commicie po wskazaniu nazwy.
- Autor
- frostiks777 ↗
- Repozytorium
- harness ↗
- 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
Wdraża jedno zadanie z listy zadań, sprawdza je, testuje i zapisuje w commicie po wskazaniu nazwy.
Oryginalny opis (EN)
Implement, self-review, test, and commit exactly one existing ai/tasks task, by slug or full date/slug id. Use when the user invokes /perform-task <name>, or the continue scheduler delegates one selected task.
Jak działa
- Resolve
- Implement
- Self-review
- Test
- Publish
- Report
Podgląd SKILL.md
--- name: perform-task description: Implement, self-review, test, and commit exactly one existing ai/tasks task, by slug or full date/slug id. Use when the user invokes /perform-task <name>, or the continue scheduler delegates one selected task. --- # Perform One Task Own exactly one task through to a committed result or an honestly recorded blocker. Do not switch to a different task, do not process the inbox, and do not start a second task after this one finishes — that's `continue`'s job. ## Resolve Find the task under `ai/tasks/` by slug or full `date/slug` id. If the name matches more than one task, list the matches and ask which one instead of guessing. Read that task's `task.md` and `state.yaml`. - `status: approved` → report the existing result and stop; don't redo it. - `status: blocked` → read why before retrying. If the blocker is resolved, continue from where it left off rather than restarting from scratch. - `status: todo` or `in-progress` → proceed. If `depends_on` names a task that isn't `approved` yet, stop and report which one is missing. Set `status: in-progress` in `state.yaml` before writing any application code (fold this into the eventual work commit if that's simpler — just don't leave the queue showing `todo` while you're actively working on it). ## Implement Read `AGENTS.md` and `.agents/shared/checks.md` completely before writing code. Make the smallest change that satisfies every line under `task.md`'s `## Acceptance`. Stay inside this task's own scope: a genuinely separate improvement you notice along the way goes into `ai/inbox.md` as a new note for a future task — it does not ride along in this diff. ## Self-review Read the complete diff yourself before running any checks. Walk it against `task.md`'s Acceptance criteria one by one. Look for obvious correctness issues and confirm the diff doesn't touch files the task had no reason to touch. ## Test Run every check in `.agents/shared/checks.md`. A check that fails only on something listed under `AGENTS.md`'s "Known baseline issues" doesn't block this task; anything your own change caused does. If a check fails because of this task's change, fix it and re-run — never report a task done with a failing check that your diff caused. Append a `## Result` section to `task.md`: ```markdown ## Result - Commands run: <exact commands> - Lint: <pass | pre-existing baseline errors only, listed> - Build: <pass | dev-mode fallback used, why> - Smoke tests: <pass | which spec(s) added/extended> - Screenshot: <path under .agents-runs/<task-id>/, for a UI change — or "n/a"> ``` ## Publish ```bash git add <exact files this task touched, plus ai/tasks/<id>/task.md and state.yaml> git commit -m "<Imperative summary> Task: <task-id>" ``` Set `status: approved` in `state.yaml` in the same commit — or `status: blocked` with the exact reason written into `task.md`, leaving the branch otherwise clean and the task resumable. Never commit a file this task didn't touch, and never commit anything under `.agents-runs/` (it's gitignored on purpose — scratch evidence, not project history). ## Report Task id, final status, files touched, checks run and their results, and anything you noticed but deliberately left out of scope (and confirmation it's now in `ai/inbox.md`).
Wersje
W bazie nie ma innych skilli o nazwie perform-task.
Migawka bazy z 13.11.2026 · wersja paczki cee748706e12 (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
- 100do-work
Wykonuje zatwierdzony plan z work/<slug>/README.md, zapisuje wyniki w work/<slug>/data/, opisuje przebieg w sekcji Results i przekazuje całość do review-work. - 100implement-tasks
Wdraża funkcję z tasks.json metodą TDD: test najpierw, potem kod przechodzący, refaktoryzacja, bramki i commit dla każdego zadania, z wykryciem poleceń test, lint i vet repozytorium. - 100break-tasks
Dzieli zaprojektowaną funkcję na atomowe zadania do jednego dnia z grafem zależności, Definition of Done i plikiem tasks.json, który czyta silnik implement-tasks. - 100loading-addressable-markdown
Wczytuje fragmenty Markdown wskazane jako ścieżka#slug-nagłówka, gdy misja, slice, dashboard lub zadanie odwołuje się do nich poza biblioteką context-pack OpenRig. - 100implement
Implementuje funkcję z pliku tasks.json metodą TDD: najpierw nieprzechodzący test, potem kod, refaktoryzacja, bramki jakości i commit dla każdego zadania. - 100tasks
Rozbija zaprojektowaną funkcję na niepodzielne zadania na jeden dzień i graf zależności oraz plik tasks.json dla silnika implementacji.