// OWNER · codejunkie99 · REPO SNAPSHOT
codejunkie99
Graph engineering for AI agents: the 9-stage knowledge-graph pipeline (translated from SEU's graduate course) + task-graph orchestration patterns, as a Claude skill with teaching mode and paste-ready workflows
STARS40+0 · 7d
FORKS5+0 · 7d
CONTRIBUTORS0maintainer graph thin
OPEN ISSUES · PRS0· 0
LICENSE—no license file
LANGUAGE—
FOUNDED—
LOCATION—
MEMBERS—
PUBLIC REPOS—
TOTAL STARS—
FOCUS—
FUNDING—
//STAR HISTORY · 12M
+0 all-time-window
Star history not yet available
We don't have a sampled star timeline for codejunkie99/graph-engineering yet. The chart populates once the daily snapshot pass collects its first data points for this repo.
//WHY IT'S TRENDING· narrative synthesis · medium confidence
codejunkie99/graph-engineering is sitting at #1578 on the trending leaderboard with a pulse of 10/100 with no cross-source channels firing yet — GitHub-stars-only signal so far.
It sits at 40 stars without a fresh weekly delta on record — the trending placement here is steady-state interest in the ai-agents category rather than a 7-day breakout.
Watch-outs: no tagged release on record (treat as pre-stable).
↻ refreshed 46m ago· next sync in 19m· sourced from 0 channels · 0 mentions / 24h
// RELATED REPOS · CROSS-SOURCE OVERLAP
▌ FAQ · answers from the data spine
What is codejunkie99/graph-engineering?
Graph engineering for AI agents: the 9-stage knowledge-graph pipeline (translated from SEU's graduate course) + task-graph orchestration patterns, as a Claude skill with teaching mode and paste-ready workflows
Who maintains graph-engineering?
Maintained by codejunkie99 (the owner) on GitHub.
When was graph-engineering created? When was the last update?
Created July 23, 2026 · last commit July 23, 2026.
How do I install graph-engineering?
Clone the repo:
git clone https://github.com/codejunkie99/graph-engineering.gitThen follow the README in the cloned directory.Is graph-engineering actively maintained?
stalled — no commits for an extended period
Created
Updated
Last commit
//COMMENTS · 0
Sign in to join the discussion