Skip to content
Narsil Workshop

Your own review panel

Narsil Check is a side panel that reviews your session before you ship: environment, connectors, CI, a branch behind its remote, dependency updates grouped by risk, vulnerabilities, and a to-do list Claude can use. Each guide explains one of its features, the design decisions behind it, and the request that started it.

Where the original request was recorded, the guide quotes it word for word. Where it was not, the guide says so and reconstructs it from the commit history.

Start the first guide

The guides

  1. 1The side panelHow Narsil Check draws a pane beside the chat with collapsible sections, a colored dot per section, folds it remembers and rows you copy with a click.
  2. 2The session's environmentHow Narsil Check shows the repository, folder, branch, Remote Control and Auto-fix, read from git and the desktop app's servers, and why it asks them so rarely.
  3. 3ConnectorsHow Narsil Check lists the session's MCP servers with their state and how many tools each has, asked once from the desktop app's own connectors server.
  4. 4Your PR's CIHow Narsil Check follows the GitHub Actions steps of the session's pull request with the gh CLI, every 10 seconds while a run goes, and stops when it ends.
  5. 5A branch behind its remoteHow Narsil Check fetches, counts the commits your branch lacks, warns at the top of the pane and brings them in with a git pull -r button.
  6. 6One adapter per ecosystemHow Narsil Check reads eleven package ecosystems through one small contract: each adapter reads its manifest, asks its registry and says how to raise a version.
  7. 7Classifying updatesHow Narsil Check sorts every outdated library into Blocked, Major version, Version bump only or Outside the Expo SDK, and why registry answers are kept six hours.
  8. 8Dependencies that block each otherHow Narsil Check finds npm upgrades that cannot go up alone: peers the new version asks for, peers installed packages ask for, and exact pins in the tree.
  9. 9The 24-hour waitWhy Narsil Check never raises a version published less than a day ago, where each registry says when a version came out, and what happens when nobody can say.
  10. 10Versions pinned on purposeHow Narsil Check reads a comment such as "# pinned: 3.7 breaks auth" in a manifest and keeps that library out of the upgrade button, with the comment as the reason.
  11. 11Explaining a major version with HaikuHow Narsil Check asks Haiku how hard a major upgrade is for this project, from the release notes and the lines that import the library, and how it keeps the model from inventing.
  12. 12Updating the trivial onesHow the Actualizar las N button raises every patch and minor at once, keeping each range operator and section, then runs the install tool of each ecosystem.
  13. 13Creating the PRHow Narsil Check turns upgraded manifests into a commit, a chore/upgrade-deps branch and a pull request opened with gh, and then returns you to the main branch.
  14. 14Vulnerabilities with OSV.devHow Narsil Check asks OSV.dev about every installed package in one batched query, rates each advisory from its own rating or its CVSS vector, and counts twin advisories once.
  15. 15To-dosHow Narsil Check keeps a per-project to-do list in an untracked JSON file, keeps it out of git, and never overwrites a damaged list without a copy.
  16. 16Tools for ClaudeHow Narsil Check gives Claude four tools over the to-do list with $.tool.register, serves them from tool.call hooks, and how the model decides when to use them.
  17. 17Kotlin, Gradle and AGP (advanced)Why a Kotlin or Android build cannot raise one tool alone, and how Narsil Check blocks Kotlin past its compiler plugins and checks the minimums between Gradle, AGP, Kotlin and Compose.