smithery/rm2thaddeus

start-dev-graph

Start, stop, or check Dev Graph services on this machine. Use when the user asks to start Dev Graph, start backend only, start full stack, restart, stop, or check Docker, Neo4j, API, or UI status, or to provide a specific Dev Graph page URL.

Installation

$ npx skills add smithery/rm2thaddeus --skill start-dev-graph

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/rm2thaddeus.

npx skills add smithery/rm2thaddeus

Browse all from smithery/rm2thaddeus

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,668 B
  • docs SUMMARY.md 264 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Start Dev Graph

Use this skill to run Dev Graph locally with the right subset of services.

Quickstart

  • Full stack: powershell -ExecutionPolicy Bypass -File skills\\start-dev-graph\\scripts\\startdevgraph.ps1 -Mode full
  • Backend only: powershell -ExecutionPolicy Bypass -File skills\\start-dev-graph\\scripts\\startdevgraph.ps1 -Mode backend

Workflow

  1. Confirm repo root
  • Require developergraph/api.py and startdev_graph.ps1.
  • If missing, stop and ask for the correct working directory.
  1. Decide the requested mode
  • full: Neo4j + API + UI
  • backend: Neo4j + API only
  • services: just Neo4j
  • frontend: only Dev Graph UI
  • status: report what is running
  • stop: stop Docker services and list any remaining processes
  1. Docker preflight
  • Check Docker CLI and Docker Compose:

- docker version - docker compose version

  • If Docker is installed but not running, say so and stop.
  1. Start sequence
  • full: run .\startdevgraph.ps1
  • backend:

- docker compose up -d neo4j - uvicorn developer_graph.api:app --host 0.0.0.0 --port 8080 --reload

  • services:

- docker compose up -d neo4j

  • frontend:

- cd tools/dev-graph-ui then npm run dev

When launching uvicorn or npm, use new terminal windows so the main session stays responsive.

  1. Status checks
  • docker compose ps
  • The script prints a port readiness summary (7474/7687/8080/3001).
  • Report URLs:

- http://localhost:3001 - http://localhost:8080/docs - http://localhost:7474 - http://localhost:3001/dev-graph/timeline - http://localhost:3001/dev-graph/structure

  1. Stop sequence
  • docker compose down
  • Remind the user to close any uvicorn or npm windows still running.

Notes

  • Docker Compose service name is neo4j in docker-compose.yml.
  • The Windows batch script uses neo4j_db; do not copy that name here.
  • Do not redirect uvicorn output to devgraphapi.log in the repo root. The app writes the same file and will raise a permission error.
  • The UI may choose port 3001 if 3000 is already in use; the script expects 3001.

Script

  • Run: powershell -ExecutionPolicy Bypass -File skills\\start-dev-graph\\scripts\\startdevgraph.ps1 -Mode full
  • Backend only: -Mode backend
  • Frontend + open page: -Mode frontend -Open -Page /dev-graph/structure
  • Note: -Open is required to open a browser; -Page alone will not open anything.