pickfit

BrowseDeveloper CLIs

GSL

Text DSL for storing graphs as versioned source of truth and deriving diagrams and reports via queries.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Go 1.26 or newer
  1. download and install prebuilt gsl-query and gsl-diagram binaries from GitHub releases

    curl -fsSL -o /tmp/gsl2.tar.gz https://github.com/dnnrly/gsl-lang/releases/download/v0.7.0/gsl-lang_0.7.0_linux_amd64.tar.gz && tar -xzf /tmp/gsl2.tar.gz -C /tmp && cp /tmp/gsl-query /tmp/gsl-diagram ~/.local/bin/

Check that it works

gsl-query version

The output should contain “gsl-query version 0.7.0”.

First thing to try

gsl-query version

Run gsl-query version to confirm the tool is installed, then pipe a .gsl file into gsl-query with a query.

What it does

  • Make diagrams and views from one graph
    How to use it
    1. Write your graph in a .gsl file using node and -> edge lines.
    2. Run gsl-query 'from *' < <file> | gsl-diagram -f mermaid -t component to get a Mermaid component diagram.
    Tested
  • Find what is affected when a service is retired
    How to use it
    1. Tag important nodes with a set, such as @critical, in your .gsl file.
    2. Run gsl-query '(subgraph node.id == "<service>" traverse in all) as BLAST | from * | (subgraph node in @critical) as CRIT | BLAST & CRIT' < <file> to list the critical edges that depend on that serv
    Tested
  • Model prerequisites between workflow edges
    How to use it
    1. Name edges with a label (such as GATE:) and link them with parent=<label> or by nesting edges in { } blocks.
    2. Run gsl-query 'subgraph edge depends on edge.stage == "<stage>" scope' < <file> to list edges that depend on a given stage.
    Tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 3 of 3 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • Keep architecture docs truthful from one canonical model
  • Reconstruct an undocumented system with provenance attributes
  • Model workflow prerequisites with edges depending on edges
  • Model financial, org and other relationship networks

An alternative to Mermaid, D2, Graphviz / DOT, Graph databases (Neo4j) and Structurizr / C4 DSL.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 0.7.0

Differences the test machine hit

  • README: go install github.com/dnnrly/gsl-lang/cmd/gsl-query@latest requires Go 1.26 or newer
    In the test: Go toolchain not available in box; used prebuilt binaries from GitHub releases (gsl-lang_0.7.0_linux_amd64.tar.gz) which need no Go

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.