Skip to content
Skills Library
DevOps & cloud · Analysis

ci-transit

/ci-transit

A transit map for your CI runs. Use when the user wants to visualize a GitHub Actions run as a subway map. Draws jobs as lines, steps as stations, and failed, cancelled or slow steps as service alerts.

Repository
transit ↗
Licence
MIT
Last repository change
20.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
48
Scripts
38
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 20.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 38 scripts in this package. Review them before installing, as Claude may execute them.
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

Scripts: core/adapters.mjs, core/build.mjs, core/cli.mjs, core/export.mjs, core/fsguard.mjs, core/gaps.mjs, core/render-frames.mjs, core/render.mjs, core/scrub.mjs, core/setup.mjs, core/still.mjs, core/tools.mjs, core/verdict.mjs, core/verify.mjs, core/vocab.mjs, src/agent-transit/adapters/normalize-agent.mjs, src/ci-transit/adapters/normalize-gh.mjs, src/ci-transit/samples/make-gh-run-sample.mjs, src/ci-t

What it does and when to use it

A transit map for your CI runs. Use when the user wants to visualize a GitHub Actions run as a subway map. Draws jobs as lines, steps as stations, and failed, cancelled or slow steps as service alerts.

Original author description

A transit map for your CI runs. Use when the user wants to visualize a GitHub Actions run as a subway map. Draws jobs as lines, steps as stations, and failed, cancelled or slow steps as service alerts.

How it works

  1. Where things are
  2. Steps
  3. Rules
  4. Sharing
Original SKILL.md headings · 41 lines, 614 words
SKILL.md preview
---
name: ci-transit
description: A transit map for your CI runs. Use when the user wants to visualize a GitHub Actions run as a subway map. Draws jobs as lines, steps as stations, and failed, cancelled or slow steps as service alerts.
---
<!-- Generated from src/ci-transit/SKILL.md; do not edit -->


# Transit

A public transit map for a GitHub Actions run.

🔒 Runs entirely on the user's machine; run data never leaves it. No telemetry, tracking or analytics. The built page makes no network requests. The only network use is the optional fetch script against the user's own GitHub account through their local `gh` CLI.

## Where things are

`<skill>` below means the folder containing this SKILL.md. Run every script from it by absolute path, e.g. `node <skill>/core/build.mjs ./run.json --format gh-actions --out ./transit-out/ci/transit.html`. Trace paths are relative to the user's working directory. Pass `--out` (build) or `--out-dir` (render) so results land in the user's working directory, not inside the skill folder.

## Steps

1. **Get one run into a file.** Use `node <skill>/src/ci-transit/scripts/fetch.mjs <run-id> [--repo owner/name] [--out run.json]`, or `--last-failed [--workflow name] [--branch b]` instead of a run id for the newest failed run. It invokes the local `gh run list` / `gh run view` commands read-only. Runs with more than 150 steps show only failed or cancelled steps as stations; pass `--max-steps 0` to build/render to show all. Or provide a synthetic or previously saved run JSON file shaped like `gh run view --json ...`.
2. **Build the page to share:** `node <skill>/core/build.mjs <run.json> --format gh-actions --share --title "CI: one run" --subtitle "SYNTHETIC sample data"`.
   Without `--out` the file is named after the title and the failing job, in `./transit-out/`, e.g. `transit-out/ci-test-node-22-service-alert.html`.
   `--share` scrubs at the strict level, refuses `--no-scrub`, and opens the page paused on the first failed step with a one-line verdict above the map.
   Idle stretches with nothing running (e.g. queue waits between jobs) longer than 20 s are shortened to 20 s so the animation isn't dead air; the header says how many were shortened and the root span keeps the wall time as `transit.wall_ms`. Pass `--max-gap-ms N` to change the cap, or `--max-gap-ms 0` for true wall-clock timing.
3. **Share it: the HTML file is the thing to share.** Give the user the file path and the verdict line the build printed, ready to paste,
   and have them drag the file into Slack (desktop and iOS open it as the interactive page) or the PR. Use the printed verdict as is. For example:
   > test (node 22) / Run unit tests failed after 6 min · SERVICE ALERT · 12 dependencies
   > `ci-test-node-22-service-alert.html` opens on the failed step. Click any station for its timing.
4. **Optional teaser (GIF + MP4):** `node <skill>/core/render.mjs <run.json> --format gh-actions --name ci --out-dir ./transit-out/ci --title "CI: one run" --subtitle "SYNTHETIC sample data"`.
5. **Check it:** `node <skill>/core/verify.mjs <run.json> --format gh-actions --name ci`.
6. Report slow steps, failed or cancelled steps, skipped jobs, and the job dependency map shown by the run.

## Rules

- Only render with the bundled scripts. If they fail, stop and report the exact error and command to rerun with more permissions. Never hand-write a substitute renderer or a look-alike GIF.
- Never upload a run or render anywhere unless the user asks.
- GitHub Actions logs and metadata can contain private repository information. Keep the input and output local; use synthetic data for examples and tests.
- `gh` is optional. A saved JSON file can always be passed directly to the core build/render scripts.

## Sharing

By default the run title (it is the PR or commit title) and the branch name are left out of the page, and values in
job and step names and messages are scrubbed (emails, tokens, URL query strings...). Pass `--keep-ci-titles` to keep
the title and branch, `--strict` for the stricter level (`--share` uses it and refuses `--no-scrub`). See request-transit's SKILL.md for the full list.
Files in this package (48)
  • LICENSE 1 KB
  • README.md 1 KB
  • SKILL.md 4 KB
  • package.json 1 KB
  • core/adapters.mjs 1 KB
  • core/build.mjs 11 KB
  • core/cli.mjs 2 KB
  • core/export.mjs 5 KB
  • core/fsguard.mjs 3 KB
  • core/gaps.mjs 2 KB
  • core/render-frames.mjs 5 KB
  • core/render.mjs 2 KB
  • core/scrub.mjs 9 KB
  • core/setup.mjs 15 KB
  • core/still.mjs 1 KB
  • core/tools.mjs 3 KB
  • core/transit.template.html 84 KB
  • core/verdict.mjs 6 KB
  • core/verify.mjs 4 KB
  • core/vocab.mjs 5 KB
  • core/fonts/OFL-Arimo.txt 4 KB
  • core/fonts/arimo-400.woff 12 KB
  • core/fonts/arimo-700.woff 12 KB
  • src/agent-transit/adapters/normalize-agent.mjs 15 KB
  • src/ci-transit/adapters/normalize-gh.mjs 7 KB
  • src/ci-transit/samples/gh-run-one-job.json 7 KB
  • src/ci-transit/samples/gh-run-sample.json 4 KB
  • src/ci-transit/samples/make-gh-run-sample.mjs 2 KB
  • src/ci-transit/scripts/fetch.mjs 3 KB
  • src/request-transit/adapters/fetch-datadog-api.mjs 3 KB
  • src/request-transit/adapters/fetch-posthog-api.mjs 4 KB
  • src/request-transit/adapters/fetch-tempo.mjs 5 KB
  • src/request-transit/adapters/fetch-xray.mjs 3 KB
  • src/request-transit/adapters/normalize.mjs 30 KB
  • src/request-transit/contracts/indexer.mjs 13 KB
  • src/request-transit/contracts/match.mjs 5 KB
  • src/request-transit/contracts/schema.mjs 3 KB
  • src/request-transit/contracts/text.mjs 3 KB
  • src/request-transit/contracts/extractors/class-validator.mjs 3 KB
  • src/request-transit/contracts/extractors/express.mjs 2 KB
  • src/request-transit/contracts/extractors/index.mjs 1 KB
  • src/request-transit/contracts/extractors/joi.mjs 2 KB
  • src/request-transit/contracts/extractors/nest.mjs 4 KB
  • src/request-transit/contracts/extractors/openapi.mjs 3 KB
  • src/request-transit/contracts/extractors/protobuf.mjs 4 KB
  • src/request-transit/contracts/extractors/topic-producer.mjs 1 KB
  • src/request-transit/contracts/extractors/ts-types.mjs 1 KB
  • src/request-transit/contracts/extractors/zod.mjs 3 KB

Versions

RepositoryScoreLicence
This page · israelvicars/transit100MIT
israelvicars/transit100MIT

Database snapshot: 13.11.2026 · package version 4de20bb0258e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100request-transit
    A public transit map for your requests. Use when the user wants to visualize, animate or share how a request moved through services, from a distributed trace (OpenTelemetry/OTLP, Datadog, PostHog, AWS X-Ray, Grafana Tempo). Draws the trace as an animated subway map (services are…
  • 100request-transit
    A public transit map for your requests. Use when the user wants to visualize, animate or share how a request moved through services, from a distributed trace (OpenTelemetry/OTLP, Datadog, PostHog, AWS X-Ray, Grafana Tempo). Draws the trace as an animated subway map (services are…
  • 90triaging-ci-failures
    Explains why a GitHub Actions run failed by showing the failed jobs and steps, the log lines that matter, how those jobs do on the default branch, whether the same commit passed elsewhere, and the commits since the last pass, using read-only GitHub requests. Use when the user…
  • 100transit-station-finder
    When the user needs to identify nearby public transit stations relative to a specific location. This skill searches for transit stations (MRT, subway, bus, etc.) within a specified radius of given coordinates, returning station names, distances, and accessibility information to…
  • 100mcore-create-issue
    Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure. Use when user shares a GitHub Actions URL and wants to file a bug report; 'create an issue for this failure', 'file a bug for this CI run', 'triage this GitHub Actions failure'. Takes a…
  • 100github-actions-inspection
    Failing step, stack trace, and test output from a completed GitHub Actions run; rerun failed jobs. Use when a CI check finished red and you need the error extracted from its log.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.