Move a review comment’s status
A review-process task moves one review-comment/1.0.0 todo’s status (address, send back, resolve, adjudicate, withdraw) through transition(), which refuses any move the named BPMN task may not make. The comment is written to the folio’s todos graph (its declared todo-feedback directory) and, with --commit, committed to the edit-set’s FEATURE branch. Refused on the base branch and on a detached HEAD.
Skills it satisfies
A skill states the capability; this Tool is one way to exercise it. Each skill’s declared input and output contract follows, where it has one.
review-comments
Reviewer comments on a folio’s edit-set, from a tagged pull-request comment to a structured todo on the review page. Covers the tag a reviewer types, how the comments are ingested into review-comment/1.0.0 todos, where the published review-comments.json comes from and when it refreshes, how a comment follows a renamed block and survives a removed one, who may change a comment’s status, and how to change this process. Use when a reviewer asks how to comment on a block, when the review page shows no comments or a wrong one, when editing the ingestion, or when a folio’s staging workflow is set up.
Source: folio-assistant-core/skills/content/content-lifecycle-ext/review-comments.md.
Also satisfied by: folio-review-comments, folio-review-coverage.
The skill declares no I/O contract (schemas/skills/review-comments/{input,output}.schema.json).
Inputs and outputs
Each port names a shared type by IRI, so two Tools for one skill can be checked for interchangeability.
| port | type | required | description | constraint | |
|---|---|---|---|---|---|
| in | id | NodeId | yes | The review comment’s id, review-pr<N>-c<commentId>. | string · pattern ^[A-Za-z_][A-Za-z0-9_-]*$ · A node id within a BPMN process, e.g. A_Implement |
| in | to | NodeId | yes | The status to move it to: open, addressed, resolved, adjudicated or withdrawn, checked by the script against that closed list. | string · pattern ^[A-Za-z_][A-Za-z0-9_-]*$ · A node id within a BPMN process, e.g. A_Implement |
| in | process | ProcessId | yes | The BPMN process whose task is making the move. | string · pattern ^[a-z][a-z0-9-]*$ · A BPMN process id, e.g. crdm-requirements |
| in | task | NodeId | yes | The task, in that process, making the move. | string · pattern ^[A-Za-z_][A-Za-z0-9_-]*$ · A node id within a BPMN process, e.g. A_Implement |
| in | decision | NodeId | The Decision that closes it. Required to resolve or adjudicate. | string · pattern ^[A-Za-z_][A-Za-z0-9_-]*$ · A node id within a BPMN process, e.g. A_Implement | |
| in | todos | RepoPath | The folio’s todos graph root. Default todos. | string · pattern ^[A-Za-z0-9._][A-Za-z0-9._/-]*$ · A path relative to the repository root. No .. segments. | |
| in | published | RepoPath | The published review-comments.json, for a comment not committed yet. | string · pattern ^[A-Za-z0-9._][A-Za-z0-9._/-]*$ · A path relative to the repository root. No .. segments. | |
| in | commit | Flag | Commit the file to the current feature branch. | boolean · A boolean switch — projects to a bare flag, with no value word | |
| in | base | Branch | The base branch a status may NOT be committed to. Default main. | string · pattern ^[A-Za-z0-9][A-Za-z0-9._/-]*$ · A git branch name | |
| out | comment | RepoPath | <todo-feedback dir>/<id>.json, the moved node. | string · pattern ^[A-Za-z0-9._][A-Za-z0-9._/-]*$ · A path relative to the repository root. No .. segments. |
Processes and tasks
Steps this Tool can carry out, because each names a skill it satisfies:
| process | step | lane | via skill |
|---|---|---|---|
| Committee review of a content change | Ingest tagged review comments | Review Coordinator | review-comments |
| Committee review of a content change | Review each slice | Review Committee | review-comments |
| Committee review of a content change | Withdraw a review comment | Review Committee | review-comments |
| Data sharing agreement document life cycle | Review the draft agreement | Reviewer (legal, policy) | review-comments |
How it is deployed and reached
- Command line. From the repository root:
bun run folio-assistant-core/scripts/review-comment-move.ts. - GitHub Actions. No workflow in this checkout runs its command.
As an API: its operation in the OpenAPI document and the MCP tool list of its layer.
| install | none |
| runtime | bun, git |
| network | no |
| when to choose it | |
|---|---|
| when | An editor or adjudicator, acting in a review-process task, has decided what happens to a reviewer’s comment and the decision must be recorded where the edit is: on the feature branch. |
| limits | Only the moves in REVIEW_TRANSITIONS, and only by the task each names. Anchor facts in a committed file are those of the last move; the published file is where re-anchoring shows. |
| cost | Reads one directory and writes one file; one git commit with --commit. |
What it is made of
| role | file | |
|---|---|---|
| definition | folio-assistant-core/tools/folio-review-comment-move/folio-review-comment-move.ts | |
| script | folio-assistant-core/scripts/review-comment-move.ts |
Linked data
The Tool is published as its own JSON-LD document at its IRI, https://litlfred.github.io/folio-assistant/folio-assistant-core/tools/folio-review-comment-move.jsonld, partOf its layer’s document. The node below is the definition this page was drawn from, and is embedded in the page as application/ld+json.
{
"@context": "https://litlfred.github.io/folio-assistant/folio-assistant-core/folio-assistant-core.context.jsonld",
"@id": "https://litlfred.github.io/folio-assistant/folio-assistant-core/tools/folio-review-comment-move.jsonld",
"@type": "https://litlfred.github.io/cat-harness/v0/ns/Tool",
"partOf": "https://litlfred.github.io/folio-assistant/folio-assistant-core/folio-assistant-core.jsonld",
"name": "folio-review-comment-move",
"title": "Move a review comment's status",
"description": "A review-process task moves one `review-comment/1.0.0` todo's status (address, send back, resolve, adjudicate, withdraw) through `transition()`, which refuses any move the named BPMN task may not make. The comment is written to the folio's todos graph (its declared `todo-feedback` directory) and, with `--commit`, committed to the edit-set's FEATURE branch. Refused on the base branch and on a detached HEAD.",
"install": {
"none": true
},
"invoke": {
"shell": "bun run folio-assistant-core/scripts/review-comment-move.ts"
},
"io": {
"inputs": [
{
"name": "id",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/NodeId",
"description": "The review comment's id, `review-pr<N>-c<commentId>`.",
"required": true,
"arg": {
"flag": "--id"
}
},
{
"name": "to",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/NodeId",
"description": "The status to move it to: open, addressed, resolved, adjudicated or withdrawn, checked by the script against that closed list.",
"required": true,
"arg": {
"flag": "--to"
}
},
{
"name": "process",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/ProcessId",
"description": "The BPMN process whose task is making the move.",
"required": true,
"arg": {
"flag": "--process"
}
},
{
"name": "task",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/NodeId",
"description": "The task, in that process, making the move.",
"required": true,
"arg": {
"flag": "--task"
}
},
{
"name": "decision",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/NodeId",
"description": "The Decision that closes it. Required to resolve or adjudicate.",
"required": false,
"arg": {
"flag": "--decision"
}
},
{
"name": "todos",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/RepoPath",
"description": "The folio's todos graph root. Default `todos`.",
"required": false,
"arg": {
"flag": "--todos"
}
},
{
"name": "published",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/RepoPath",
"description": "The published `review-comments.json`, for a comment not committed yet.",
"required": false,
"arg": {
"flag": "--published"
}
},
{
"name": "commit",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/Flag",
"description": "Commit the file to the current feature branch.",
"required": false,
"arg": {
"flag": "--commit"
}
},
{
"name": "base",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/Branch",
"description": "The base branch a status may NOT be committed to. Default `main`.",
"required": false,
"arg": {
"flag": "--base"
}
}
],
"outputs": [
{
"name": "comment",
"schema": "https://litlfred.github.io/folio-assistant/cat-harness/tool-types.schema.json#/$defs/RepoPath",
"description": "`<todo-feedback dir>/<id>.json`, the moved node."
}
]
},
"satisfies": [
"review-comments"
],
"requirements": {
"runtime": [
"bun",
"git"
],
"network": false
},
"selection": {
"when": "An editor or adjudicator, acting in a review-process task, has decided what happens to a reviewer's comment and the decision must be recorded where the edit is: on the feature branch.",
"limits": "Only the moves in `REVIEW_TRANSITIONS`, and only by the task each names. Anchor facts in a committed file are those of the last move; the published file is where re-anchoring shows.",
"cost": "Reads one directory and writes one file; one git commit with `--commit`."
}
}