You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 01373b8
Browse filesBrowse the repository at this point in the historyBrowse files
Fixes and additions from testing 0.9 on a real project.
- `ado_create`: fields with a default of the process (Value Area, Severity, Triage…) and fields Azure DevOps fills
itself (Area ID, Iteration ID, State, Work Item Type) are no longer asked for - the rule check of 0.9.0 took the
system rules of the process for fields to give. A rule "required while State was empty" is checked as "on create"
instead of ending in a 400 from Azure DevOps.
- `ado_fields type=<type>`: fields required by rules are named as REQUIRED, and fields that are required but filled by
Azure DevOps say so.
- `ado_trace` much faster on items with many pull requests: the files of a PR come from its last iteration instead of
a diff of its merge commit, merge commits of linked PRs are not read twice, a completed PR into a branch answers
"is it there" without asking, and only the newest change of each source -> target pair is checked. Reading the
changes gets half of the time, so builds and deployments are still read.
- `ado_trace` with no code linked looks for configuration words in every text field of the item and its tasks.
- `ado_sprint`: a "Done" state that the process puts in the Resolved category counts as done.
- `ado_work_item`: names of up to 40 linked releases (was 10); a release deleted by retention or not readable says so.
- Numbered lists keep their numbering (`<ol start="3">`).
- `ado_pr_update`: `update` adds reviewers, `requiredReviewers` (on create and update) makes them required,
`autocomplete` (merge strategy, delete source branch, text = merge message) and `cancel_autocomplete`.
- A parameter a tool does not have is reported with the tool's parameters instead of being dropped (a conversation
started before an update still sees the old tool descriptions).
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -218,7 +218,7 @@ What each MCP tool answers, when Claude should reach for it, and the CLI command
218
218
|`ado_trace`| was it done as asked, and where is it: the acceptance criteria (from the parent for a task) and whether they changed after coding started; changesets, commits and pull requests linked to the item and its tasks with the X++ objects they touch; builds (also those deleted by retention); every release stage of the code's branches with **YES / NOT YET**, labelled by the environment map (`staging` → UAT); for Git, whether the change is merged into each mapped branch; tests, tasks and warning signals | "did they do what I asked", "is it on UAT yet" |`adolens trace 123`|
219
219
|`ado_changes`| the files of a changeset (`523`), pull request (`PR 482`) or commit (sha + `repo`) with X++ objects and their added / changed / removed methods; `file` gives the diff of one file — for AOT XML per method plus the metadata (fields, controls, properties) without raw XML noise | reading what exactly changed |`adolens changes 523`, `adolens changes 523 --file AxClass/SalesTable_Extension.xml`|
220
220
|`ado_pr`| without id: pull requests waiting for my review and mine (`list=active`: all); `merged=<branch>`: those completed into a branch (`since`, `top`, `repo`) with their work items; with id: status, reviewers and votes, checks (build, work item linking, reviewers), linked work items, open comment threads written by people (not system notes) | code review, "what is blocking my PR" |`adolens pr`, `adolens pr 482`|
221
-
|`ado_pr_update`|`create` (repo, source, target, title, markdown text, work items, reviewers, draft, tags), `update` (title, description, link work items - for branch policies), `comment` (general or on a file and line), `reply`, `resolve`, `vote`, `tag`, `publish`, `complete`, `abandon`; `@[name]` notifies | reviewing, opening and finishing PRs | — |
221
+
|`ado_pr_update`|`create` (repo, source, target, title, markdown text, work items, reviewers, draft, tags), `update` (title, description, reviewers, link work items - for branch policies), `autocomplete` / `cancel_autocomplete` (merge strategy, delete the source branch, merge message), reviewers optional or required, `comment` (general or on a file and line), `reply`, `resolve`, `vote`, `tag`, `publish`, `complete`, `abandon`; `@[name]` notifies | reviewing, opening and finishing PRs | — |
222
222
|`ado_pipeline`| recent builds (of a pipeline, a branch); with `build`: the failed stage, job and steps, their errors, and the lines of the log that report errors (MSBuild noise cut); `artifacts=true` lists the build's artifacts, `artifact=<name>` the files in one (`part=` reads a file), `save=true` saves it to disk | "why is the build red", getting a package or a log |`adolens pipeline 900`, `adolens pipeline 900 --artifact drop --save`|
223
223
|`ado_pipeline_run`| queues a pipeline by name or id, optionally on a branch, with variables | re-running a build | — |
224
224
|`ado_wiki`| the project wiki: page tree (`depth`), one page as markdown with its version and subpages, or search across the project's wikis with snippets; long pages are cut unless `detail=full`| "how does X work", finding documentation |`adolens wiki`, `adolens wiki "Team/Setup"`, `adolens wiki --search "dual write"`|
Copy file name to clipboardExpand all lines: README.pl.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -219,7 +219,7 @@ Na co odpowiada każde narzędzie MCP, kiedy Claude powinien po nie sięgnąć i
219
219
|`ado_trace`| czy zrobiono to, o co proszono, i gdzie to jest: kryteria akceptacji (dla zadania — z elementu nadrzędnego) i to, czy zmieniły się po rozpoczęciu prac; changesety, commity i pull requesty podpięte pod element i jego zadania, z obiektami X++, których dotyczą; buildy (także usunięte przez retencję); każdy etap release'u gałęzi tego kodu z **TAK / JESZCZE NIE** i etykietą z mapy środowisk (`staging` → UAT); dla Gita — czy zmiana jest scalona do każdej zmapowanej gałęzi; testy, zadania i sygnały ostrzegawcze | „czy zrobili to, o co prosiłem”, „czy to już jest na UAT” |`adolens trace 123`|
220
220
|`ado_changes`| pliki changesetu (`523`), pull requesta (`PR 482`) albo commita (sha + `repo`) z obiektami X++ i ich dodanymi / zmienionymi / usuniętymi metodami; `file` daje diff jednego pliku — dla AOT XML per metoda plus metadane (pola, kontrolki, właściwości) bez szumu surowego XML-a | czytanie, co dokładnie się zmieniło |`adolens changes 523`, `adolens changes 523 --file AxClass/SalesTable_Extension.xml`|
221
221
|`ado_pr`|`merged=<gałąź>`: pull requesty scalone do gałęzi (`since`, `top`, `repo`) z ich work itemami; bez id: pull requesty czekające na mój przegląd i moje (`list=active`: wszystkie); z id: stan, recenzenci i głosy, kontrole (build, podpięty work item, recenzenci), podpięte work itemy, otwarte wątki pisane przez ludzi (bez wpisów systemowych) | code review, „co blokuje mój PR” |`adolens pr`, `adolens pr 482`|
222
-
|`ado_pr_update`|`create` (repo, źródło, cel, tytuł, opis w markdownie, work itemy, recenzenci, szkic, tagi), `update` (tytuł, opis, podpięcie work itemów - pod polityki gałęzi), `comment` (ogólny albo na pliku i linii), `reply`, `resolve`, `vote`, `tag`, `publish`, `complete`, `abandon`; `@[imię]` wysyła powiadomienie | przegląd, zakładanie i kończenie PR-ów | — |
222
+
|`ado_pr_update`|`create` (repo, źródło, cel, tytuł, opis w markdownie, work itemy, recenzenci, szkic, tagi), `update` (tytuł, opis, recenzenci, podpięcie work itemów - pod polityki gałęzi), `autocomplete` / `cancel_autocomplete` (strategia scalenia, usunięcie gałęzi źródłowej, komunikat), recenzenci opcjonalni albo wymagani, `comment` (ogólny albo na pliku i linii), `reply`, `resolve`, `vote`, `tag`, `publish`, `complete`, `abandon`; `@[imię]` wysyła powiadomienie | przegląd, zakładanie i kończenie PR-ów | — |
223
223
|`ado_pipeline`| ostatnie buildy (pipeline'u, gałęzi); z `build`: nieudany etap, zadanie i kroki, ich błędy i linie logu zgłaszające błędy (bez szumu MSBuild); `artifacts=true` lista artefaktów buildu, `artifact=<nazwa>` pliki w nim (`part=` czyta plik), `save=true` zapisuje go na dysk | „czemu build jest czerwony”, pobranie paczki lub logu |`adolens pipeline 900`, `adolens pipeline 900 --artifact drop --save`|
224
224
|`ado_pipeline_run`| uruchamia pipeline po nazwie albo id, opcjonalnie na gałęzi, ze zmiennymi | ponowne puszczenie buildu | — |
225
225
|`ado_wiki`| wiki projektu: drzewo stron (`depth`), strona jako markdown z wersją i podstronami albo wyszukiwanie we wszystkich wiki projektu z fragmentami; długie strony są ucinane, chyba że `detail=full`| „jak działa X”, szukanie dokumentacji |`adolens wiki`, `adolens wiki "Team/Setup"`, `adolens wiki --search "dual write"`|
0 commit comments