Przejdź do treści
Biblioteka skilli
Programowanie · Automatyzacja

qargi-task

/qargi-task

Przekazuje jednorazowe zadanie programistyczne agentowi działającemu na własnej kopii, który zwraca poprawki, i prowadzi jego sesję w chmurze.

Repozytorium
qargi ↗
Licencja
MIT
Ostatnia zmiana repozytorium
12.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
3
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Przekazuje jednorazowe zadanie programistyczne agentowi działającemu na własnej kopii, który zwraca poprawki, i prowadzi jego sesję w chmurze.

Wyzwalacze z opisu

<task><check>

Argumenty

/qargi-task <task>" --done "<check>" [--instance NAME] [--base B] [--scope PATHS] | send|start|status|watch|collect|stop|close ...
Oryginalny opis (EN)

Hand a one-off development task (build, write, review or test) to a member that works in its own clone and returns patches, with /qargi-task "<task>" --done "<check>". Use when the user asks to dispatch, delegate or run a task through an agent, or to drive the session of a named cloud instance (send, watch, collect, stop, close). Local by default; cloud only when the request names an instance. Taking the patches in is /qargi-verify; a team run is /qargi-team.

Jak działa

  1. Quick form
  2. Hard rules
  3. Task block
  4. Profiles
  5. Local flow
  6. Parallel tasks
Sekcje z nagłówków SKILL.md, w oryginale · 38 linii, 764 słów
Podgląd SKILL.md
---
name: qargi-task
description: Hand a one-off development task (build, write, review or test) to a member that works in its own clone and returns patches, with /qargi-task "<task>" --done "<check>". Use when the user asks to dispatch, delegate or run a task through an agent, or to drive the session of a named cloud instance (send, watch, collect, stop, close). Local by default; cloud only when the request names an instance. Taking the patches in is /qargi-verify; a team run is /qargi-team.
argument-hint: '"<task>" --done "<check>" [--instance NAME] [--base B] [--scope PATHS] | send|start|status|watch|collect|stop|close ...'
---

# /qargi-task (dispatch and session lifecycle)

A **role** says what a task is for (`qargi role list`): build, write, review and test ship with qargi; add your own in `~/.qargi/config/roles/NAME/`. Its **class** (write or read-only) is what the guard checks; its text cannot change it. A **member** is a local agent you named and gave roles (`qargi agent add`), written by the project's local runtime from one member definition (`/qargi-instances`); an **instance** is a registered cloud agent of one role. All of them obey `contract/contract.md`: one task, own clone, patches back, never push, no backlog.

## Quick form

`/qargi-task "<task>" --done "<executable check>" [--role ROLE] [--instance NAME] [--base BRANCH] [--scope PATHS]`

If the first argument is not a session verb (`send`, `start`, `status`, `watch`, `collect`, `stop`, `close`: load `cloud.md`), it is a task: dispatch it to the member that serves its role (`qargi agent for ROLE`, whose first word is the member). `--role` defaults to build. Inside a feature, use `--base feature/NAME` and run `qargi marshal check NAME` first; `/qargi-flow` owns the rest.

## Hard rules

- **Local is the default.** Load cloud.md only when the user's request names a cloud instance; never choose cloud on your own or fall back between local and cloud: report instead.
- Agents never push. What the guard refuses: `qargi help guard`. Plan and token rules: `qargi help approvals`.
- Every returned series goes through `/qargi-verify` before anything is applied.

## Task block

`qargi local prepare` writes `RUN/task.md` with ROLE, TASK, DONE, BASE and SCOPE; never write one by hand. It prints `ROLE`, `CLASS`, `PROFILE`, `CONTRACT` and the paths. BASE defaults to the dispatching session's branch; name it on master or develop. DONE is executable and runs on final HEAD after all outcomes, and again after later changes; obtain a command for prose. Supply passing baseline evidence in TASK with exact BASE_SHA, matching check and input definitions, reference and provenance; the member records it in deviations[], never as gates[] pass. Cloud blocks (cloud.md) have the same sections.

## Profiles

A profile holds a repository's gates, rules and coordinator review steps, in `~/.qargi/config/profiles/<name>.md` (`<name>` is the repository directory's name), never in the project. `prepare` inlines its text as PROFILE (`qargi project profile check` lints it). `--profile` on `send` and `local prepare` is the role's model profile, not this file. No profile is fine; nothing qargi related is added to a project's committed files.

## Local flow

1. Write the task to a scratch file with your file tool, then `qargi local prepare --repo <repo> --base <base> --slug <slug> --scratch <scratchpad> --role <role> --task-file <file> --done "<command>" [--scope <path>]... [--profile <profile>]` makes the run: a clone on `agent/<slug>` of a bare copy with no remote, an output directory, a credential-less `git` wrapper and `RUN/task.md`. It refuses a prose DONE (its first word must be an executable, a builtin or a BASE script) and an empty or linked task file. It prints `TASK_FILE`, `RUN`, `MEMBER`, `MODEL`, `EFFORT` and the paths. The executor sees only the committed memory. For a private repository not checked out here, use `--repo-url URL --credential-file FILE` in place of `--repo`.
2. Start the member as the project's local runtime says (`qargi provider show RUNTIME`), handing it the path of `RUN/task.md`: read it and follow it.
   - **In-session runtime.** Take MEMBER, MODEL and EFFORT from step 1 (or `qargi agent for <role> [--profile NAME]`). Spawn it as `qargi provider notes spawn` says, with that brief plus the four paths (`CLONE`, `OUT`, `GIT`, `BASE_SHA`) if the runtime needs them. No member serves the role: ask the user to add one (`qargi agent add NAME --roles <role> --project P`), never use another agent type. A member `qargi agent list` shows `STALE` or `DRIFT` is out of date: tell the user, and `qargi agent refresh NAME` only with their go-ahead.
   - **Command runtime** (`dispatch.mode` is command: a headless CLI, no member file): load `local-run.md`.
3. When it reports, run `qargi local verify <RUN>` first: a change in the real repository's refs means stop and tell the user.
4. Then `/qargi-verify` on `OUT`: it takes the work in.

## Parallel tasks

Split a change into tasks whose paths do not overlap and dispatch them together (one `prepare` and one member launch each, in one message, every task with its own `--slug`, `SCOPE` and `TMP`). Give each task the narrowest executable `DONE` (a test file or a script, not the suite); you run the full suite once, after the tasks of a collection are merged. Tasks that touch the same file go one after the other, the second based on the first's merge.
Pliki w paczce (3)
  • SKILL.md 5 KB
  • cloud.md 5 KB
  • local-run.md 1 KB

Wersje

W bazie nie ma innych skilli o nazwie qargi-task.

Migawka bazy z 13.11.2026 · wersja paczki 502bdf871826 (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

  • 90qargi-verify
    Przyjmuje poprawki zwrócone przez agentów: sprawdza każde uruchomienie, stosuje je na roboczej gałęzi i scala dopiero po zgodzie użytkownika.
  • 86done
    Zamyka zadanie programistyczne: sprawdza, czy jest gotowe, i przygotowuje je do przekazania albo zamknięcia.
  • 100warp-delegate
    Przekazuje zadanie programistyczne agentowi Warp CLI do wykonania w tle, a potem sam przegląda diff i wprowadza zmiany.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.