torrust · josecelano · Apr 28, 2026 · Apr 22, 2026 · Apr 22, 2026 · Apr 22, 2026
@@ -0,0 +1,91 @@
+---
+name: fetch-review-threads
+description: Fetch unresolved GitHub pull request review thread IDs for the torrust-tracker project. Use when asked to find open PR review threads, list unresolved review comments, collect thread IDs before resolving suggestions, or inspect Copilot review feedback. Triggers on "fetch review threads", "list unresolved PR comments", "get review thread IDs", or "find open review suggestions".
+metadata:
+  author: torrust
+  version: "1.0"
+---
+
+# Fetching PR Review Threads
+
+Use this skill before resolving review feedback. Its purpose is to collect the unresolved
+review thread IDs and enough context to decide whether each thread should stay open or be closed.
+
+## Preferred Sources
+
+Use one of these approaches:
+
+1. Active pull request tools when they are available in the environment.
+2. GitHub CLI GraphQL when you need a terminal-based fallback.
+
+Prefer the active PR tools first because they provide thread metadata together with file paths,
+resolution state, and comments.
+
+## What to Collect
+
+For each unresolved thread, capture:
+
+- thread ID
+- file path
+- `isResolved`
+- `canResolve`
+- comment author
+- comment body
+
+Only unresolved threads should be considered for follow-up work.
+
+## Active PR Tool Workflow
+
+1. Read the active PR.
+2. Inspect the `reviewThreads` array.
+3. Filter to threads where `isResolved == false`.
+4. Group them by file if you plan to address them in code.
+
+## GitHub CLI GraphQL Fallback
+
+Use GitHub CLI if you need to retrieve threads directly from the terminal.
+
+```bash
+gh api graphql \
+  -F owner=torrust \
+  -F repo=torrust-tracker \
+  -F pullNumber=1707 \
+  -f query='query($owner: String!, $repo: String!, $pullNumber: Int!) {
+    repository(owner: $owner, name: $repo) {
+      pullRequest(number: $pullNumber) {
+        reviewThreads(first: 100) {
+          nodes {
+            id
+            isResolved
+            isOutdated
+            comments(first: 20) {
+              nodes {
+                author {
+                  login
+                }
+                body
+                path
+              }
+            }
+          }
+        }
+      }
+    }
+  }'
+```
+
+Then filter for unresolved threads.
+
+## Practical Guidance
+
+- Do not guess thread IDs.
+- Do not resolve a thread immediately after fetching it. First confirm the fix exists.
+- If a thread is outdated but unresolved, still read it before deciding what to do.
+- If there are more than 100 threads, paginate instead of assuming the first page is complete.
+
+## Completion Checklist
+
+- [ ] Unresolved thread IDs were collected from the current PR state
+- [ ] Each thread has enough context for triage
+- [ ] Already resolved threads were excluded from action items
+- [ ] The result is ready to hand off to a fix or resolution workflow
@@ -0,0 +1,77 @@
+---
+name: resolve-review-threads
+description: Resolve addressed GitHub pull request review threads for the torrust-tracker project. Use when asked to mark PR suggestions as resolved, resolve review comments, close addressed review threads, or clear Copilot review feedback after fixes are pushed. Triggers on "resolve PR threads", "mark suggestions as resolved", "resolve review comments", or "close addressed review threads".
+metadata:
+  author: torrust
+  version: "1.0"
+---
+
+# Resolving PR Review Threads
+
+Use this skill after the requested code or documentation changes are already implemented,
+validated, committed, and pushed.
+
+## Preconditions
+
+- The feedback has actually been addressed in the branch.
+- Validation has been run for the touched scope (`linter all`, tests, or a targeted executable check).
+- You have the target PR number and unresolved review thread IDs.
+
+Do not resolve a thread just because a suggestion exists. Resolve it only when the underlying
+concern is fixed or intentionally declined with a clear reason.
+
+## Workflow
+
+1. Read the active PR and collect unresolved review threads.
+2. Group threads by file and confirm each one is truly addressed.
+3. Implement and validate any missing fixes before resolving anything.
+4. Resolve the addressed threads.
+5. Re-check the PR state if needed.
+
+## Preferred Resolution Path
+
+If PR tools are available, first gather thread IDs from the active pull request metadata.
+
+- Use the active PR tools to identify unresolved `reviewThreads`.
+- Resolve only threads where `isResolved == false` and the fix is already on the branch.
+
+## GitHub CLI GraphQL Command
+
+Use GitHub CLI GraphQL when you need to resolve a thread directly from the terminal:
+
+```bash
+gh api graphql \
+  -F threadId=THREAD_ID \
+  -f query='mutation($threadId: ID!) { resolveReviewThread(input: { threadId: $threadId }) { thread { isResolved } } }'
+```
+
+Successful output should report `isResolved: true`.
+
+## Batch Pattern
+
+For multiple threads, resolve them one by one and check each result:
+
+```bash
+for thread_id in \
+  THREAD_ID_1 \
+  THREAD_ID_2
+do
+  gh api graphql \
+    -F threadId="$thread_id" \
+    -f query='mutation($threadId: ID!) { resolveReviewThread(input: { threadId: $threadId }) { thread { isResolved } } }'
+done
+```
+
+## Notes
+
+- Thread IDs are GraphQL node IDs, not PR numbers or comment IDs.
+- This resolves the review thread, not the entire review.
+- If a thread should remain open, leave it open and explain why.
+- If you do not know the thread IDs yet, query the active PR first instead of guessing.
+
+## Completion Checklist
+
+- [ ] All targeted threads were verified against the current branch state
+- [ ] Validation passed before resolution
+- [ ] Each resolved mutation returned `isResolved: true`
+- [ ] Any intentionally unresolved feedback is documented with reasoning
@@ -168,27 +168,33 @@ jobs:
     name: E2E
     runs-on: ubuntu-latest
     needs: database-compatibility
+    timeout-minutes: 45
 
     strategy:
       matrix:
         toolchain: [nightly, stable]
 
     steps:
-      - id: setup
+      - id: setup-e2e-toolchain
         name: Setup Toolchain
         uses: dtolnay/rust-toolchain@stable
         with:
           toolchain: ${{ matrix.toolchain }}
           components: llvm-tools-preview
 
-      - id: cache
+      - id: enable-e2e-job-cache
         name: Enable Job Cache
         uses: Swatinem/rust-cache@v2
 
-      - id: checkout
+      - id: checkout-repository
         name: Checkout Repository
         uses: actions/checkout@v6
 
-      - id: test
+      - id: run-tracker-e2e-tests
         name: Run E2E Tests
         run: cargo run --bin e2e_tests_runner -- --config-toml-path "./share/default/config/tracker.e2e.container.sqlite3.toml"
+
+      - id: run-qbittorrent-e2e-test
+        if: matrix.toolchain == 'stable'
+        name: Run qBittorrent E2E Test
+        run: cargo run --bin qbittorrent_e2e_runner -- --compose-file ./compose.qbittorrent-e2e.yaml --timeout-seconds 600
diff --git a/AGENTS.md b/AGENTS.md
@@ -180,6 +180,19 @@ See [docs/benchmarking.md](docs/benchmarking.md) and [docs/profiling.md](docs/pr
 The project uses the `linter` binary from
 [torrust/torrust-linting](https://github.com/torrust/torrust-linting).
 
+Agent reminder:
+
+- When asked to lint, prefer loading the `run-linters` skill at
+  `.github/skills/dev/git-workflow/run-linters/SKILL.md`.
+- Start with `linter all`.
+- To lint only markdown files, run `linter markdown`.
+- To isolate a failing tool, run the individual linters directly:
+  `linter markdown`, `linter yaml`, `linter toml`, `linter cspell`, `linter clippy`,
+  `linter rustfmt`, `linter shellcheck`.
+- If `linter all` fails or appears inconclusive, use the individual commands above before editing
+  files so the failing linter is explicit.
+- Treat `linter all` passing with exit code `0` as the required pre-commit gate.
+
 ```sh
 # Install the linter binary
 cargo install --locked --git https://github.com/torrust/torrust-linting --bin linter