Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
List unresolved review threads for the pull request recorded in workflow state.
Install List Review Threads
$ npx skills add NTCoding/living-architecture --skill list-review-threads -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NTCoding/living-architecture list-review-threads --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NTCoding/living-architecture.git skills-src && mkdir -p .claude/skills && cp -r skills-src/tools/dev-workflow-v2/skills/list-review-threads .claude/skills/list-review-threads && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "list-review-threads" agent skill from https://github.com/NTCoding/living-architecture/tree/main/tools/dev-workflow-v2/skills/list-review-threads into .claude/skills/list-review-threads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "list-review-threads", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NTCoding/living-architecture/tree/main/tools/dev-workflow-v2/skills/list-review-threadsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NTCoding/living-architecture --skill list-review-threads -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NTCoding/living-architecture list-review-threads --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NTCoding/living-architecture.git skills-src && mkdir -p .agents/skills && cp -r skills-src/tools/dev-workflow-v2/skills/list-review-threads .agents/skills/list-review-threads && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "list-review-threads" agent skill from https://github.com/NTCoding/living-architecture/tree/main/tools/dev-workflow-v2/skills/list-review-threads into .agents/skills/list-review-threads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "list-review-threads", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NTCoding/living-architecture --skill list-review-threads -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NTCoding/living-architecture list-review-threads --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NTCoding/living-architecture.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/tools/dev-workflow-v2/skills/list-review-threads .cursor/skills/list-review-threads && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "list-review-threads" agent skill from https://github.com/NTCoding/living-architecture/tree/main/tools/dev-workflow-v2/skills/list-review-threads into .cursor/skills/list-review-threads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "list-review-threads", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NTCoding/living-architecture.git --path tools/dev-workflow-v2/skills/list-review-threads--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NTCoding/living-architecture --skill list-review-threads -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NTCoding/living-architecture list-review-threads --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NTCoding/living-architecture.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/tools/dev-workflow-v2/skills/list-review-threads .gemini/skills/list-review-threads && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "list-review-threads" agent skill from https://github.com/NTCoding/living-architecture/tree/main/tools/dev-workflow-v2/skills/list-review-threads into .gemini/skills/list-review-threads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "list-review-threads", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NTCoding/living-architecture list-review-threadsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NTCoding/living-architecture --skill list-review-threads -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NTCoding/living-architecture.git skills-src && mkdir -p .github/skills && cp -r skills-src/tools/dev-workflow-v2/skills/list-review-threads .github/skills/list-review-threads && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "list-review-threads" agent skill from https://github.com/NTCoding/living-architecture/tree/main/tools/dev-workflow-v2/skills/list-review-threads into .github/skills/list-review-threads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "list-review-threads", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NTCoding/living-architecture --skill list-review-threads -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NTCoding/living-architecture list-review-threads --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NTCoding/living-architecture.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/tools/dev-workflow-v2/skills/list-review-threads .opencode/skills/list-review-threads && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "list-review-threads" agent skill from https://github.com/NTCoding/living-architecture/tree/main/tools/dev-workflow-v2/skills/list-review-threads into .opencode/skills/list-review-threads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "list-review-threads", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
list-review-threads- GitHub stars
- 139
- Token cost
- ~400 tokens
- SKILL.md length
- 171 words
- Files
- 2
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
List unresolved review threads for the pull request recorded in workflow state.
- Works in 7 steps: Detect the current harness before… → Run the selected harness's get-state… → Stop if prNumber is missing. Do not… → …
- Tasks that involve Pull requests
- Calls pnpm
What it does
List Review Threads is an agent skill from NTCoding/living-architecture. List unresolved review threads for the pull request recorded in workflow state. Use only when explicitly invoked as the list-review-threads skill.
Its SKILL.md is about 400 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development, covering Pull requests. The repository describes itself as: Extra software architecture from your code as living documentation. AI-assisted. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Pull requests
Example prompts
- “/list-review-threads”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Detect the current harness before reading review threads
- Run the selected harness's get-state workflow operation and extract prNumber.
- Stop if prNumber is missing. Do not infer a PR from the current branch.
- Fetch the PR URL, reviewDecision, reviews, and reviewThreads through GitHub GraphQL. Paginate the reviews, review threads, and every…
- Keep unresolved review threads only and group them by file path. Use no file when a thread has no path.
- For every unresolved thread, report its thread ID, file path, line when present, comment authors in chronological order, and the latest…
- Return exactly this report shape
What it can do on your machine
Read from SKILL.md and the folder at commit a24bc9f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
List Review Threads loads about 400 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 171 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from NTCoding/living-architecture at commit a24bc9f, republished under its Apache-2.0 licence (© NTCoding). 171 words, ~400 tokens.
Download SKILL.mdSave it as
.claude/skills/list-review-threads/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- list-review-threads
- description
- List unresolved review threads for the pull request recorded in workflow state. Use only when explicitly invoked as the list-review-threads skill.
List Review Threads
- Detect the current harness before reading review threads:
- If
CODEX_THREAD_IDis present, run workflow operations withpnpm --dir tools/dev-workflow-v2 run codex-workflow <operation> [args]. - Otherwise, if
PI_CODING_AGENT=trueis present, run workflow operations with theworkflowtool. - Otherwise, run workflow operations with
/dev-workflow-v2:workflow <operation> [args].
- If
- Run the selected harness's
get-stateworkflow operation and extractprNumber. - Stop if
prNumberis missing. Do not infer a PR from the current branch. - Fetch the PR URL,
reviewDecision, reviews, andreviewThreadsthrough GitHub GraphQL. Paginate the reviews, review threads, and every thread's comments connection untilpageInfo.hasNextPageis false. - Keep unresolved review threads only and group them by file path. Use
no filewhen a thread has no path. - For every unresolved thread, report its thread ID, file path, line when present, comment authors in chronological order, and the latest comment body selected by greatest
createdAt. - Return exactly this report shape:
PR: #<number> <url>
Unresolved threads: <count>
## <file path or "no file">
- Thread: <id>
Line: <line or —>
Authors: <author1>, <author2>
Latest comment: <summary>This skill is read-only. Do not reply to or resolve threads, and do not record workflow state.
© NTCoding, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in tools/dev-workflow-v2/skills/list-review-threads of NTCoding/living-architecture.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit a24bc9f
Compare with similar skills
List Review Threads next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| List Review Threads this skillNTCoding/living-architecture | 139 | — | ~400 | Automated safety check: Pass | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
More from NTCoding/living-architecture
Ddd
NTCoding/living-architecture
Explore and evaluate domain models collaboratively before implementation.
Dev Workflow Start Implementation
NTCoding/living-architecture
Start implementation for a GitHub issue. An agent skill from NTCoding/living-architecture.
Workflow
NTCoding/living-architecture
Execute a low-level dev-workflow-v2 state operation. An agent skill from NTCoding/living-architecture.
Related
Categories
Questions about List Review Threads
What does List Review Threads do?
List unresolved review threads for the pull request recorded in workflow state. List Review Threads is an agent skill from NTCoding/living-architecture. List unresolved review threads for the pull request recorded in workflow state.
When should I use List Review Threads?
List Review Threads fits situations like: tasks that involve Pull requests.
How do I install List Review Threads in Claude Code?
Run `npx skills add NTCoding/living-architecture --skill list-review-threads -a claude-code`. Or copy the skill folder (tools/dev-workflow-v2/skills/list-review-threads in NTCoding/living-architecture) into .claude/skills/list-review-threads in your project. Claude Code loads it when a task matches its description.
How do I install List Review Threads in Codex?
Run `npx skills add NTCoding/living-architecture --skill list-review-threads -a codex`. Or copy the skill folder (tools/dev-workflow-v2/skills/list-review-threads in NTCoding/living-architecture) into .agents/skills/list-review-threads in your project. Codex loads it when a task matches its description.
Can I use List Review Threads in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NTCoding/living-architecture --skill list-review-threads -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/list-review-threads, .gemini/skills/list-review-threads, .github/skills/list-review-threads and .opencode/skills/list-review-threads in your project.
What does List Review Threads need to run?
Going by SKILL.md and its folder, List Review Threads needs the command-line tools its instructions call (pnpm).
Does List Review Threads access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is List Review Threads safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does List Review Threads use?
List Review Threads is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does List Review Threads use?
About 400 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to List Review Threads?
Skills that share tags, products or a category with List Review Threads: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains List Review Threads?
NTCoding (a GitHub user) maintains it in NTCoding/living-architecture, which has 139 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 5, 2026.
Source: NTCoding/living-architecture on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.