Skip to content

devfolio v0.2.0 Release Notes

Release Date: 2026-07-20

Overview

DevFolio's second release adds a third command group — DevX usage dashboards, built on the OmniDevX ecosystem's canonical event model — alongside improvements to the existing contributor profile command and a full MkDocs documentation site.

Highlights

  • devfolio devx dashboard — reads events already collected into the local OmniDevX store (Claude Code, Codex CLI, git, and GitHub, all normalized into one canonical model by omnidevx-core), builds a DeveloperPeriodReport, and exports a portable dashforge dashboard: 8 headline metric tiles, daily activity/cost charts, and a source-coverage table.
  • MkDocs documentation site — landing page, getting-started walkthrough, and a full command reference, matching the structure already used by omnidevx-core, omni-github, omnidevx, and dashforge.
  • Contributor profile improvements — local git clone detection (uses git log on a local clone when available, falls back to the GitHub API automatically), multi-stage progress reporting, and a --dashboard flag exporting a dashforge-compatible dashboard.

What's New

DevX Dashboard

devfolio devx dashboard --person person:jane --days 30 -o dashboard.json

Unlike contributor profile --dashboard, this export is built directly against dashforge's dashboardir Go package rather than a local reimplementation, so its chart widgets render correctly in dashforge's current viewer. It's also the first command in DevFolio that doesn't call the GitHub API at all — it only reads the local OmniDevX store.

The output can be opened in dashforge's static viewer, validated with dashforge validate, or served through VisionStudio's DevX panel by writing it to ~/.plexusone/omnidevx/dashboard.json.

See DevX Commands.

Contributor Profile: Local Detection and Dashboards

# Uses local clones when found, falls back to the API automatically
devfolio contributor profile --user grokify -o profile.json

# Force API-only mode
devfolio contributor profile --user grokify --api-only -o profile.json

# Export as a dashforge dashboard
devfolio contributor profile --user grokify --dashboard -o dashboard.json

Local detection is faster, avoids GitHub API rate limits, and sees full commit messages for AI co-author trailer detection. See Contributor Commands — including a known gap: --dashboard's chart widgets (language pie chart, AI-tools bar chart) don't currently render in dashforge's viewer, unlike devx dashboard's export.

Documentation Site

Full site at https://plexusone.github.io/devfolio: a landing page, getting-started walkthrough, and command reference for all three groups (contributor, team, devx). The ecosystem architecture specs (docs/specs/PRD.md, TRD.md, PLAN.md, ROADMAP.md) are deliberately excluded from the built site — they're written for contributors working on the OmniDevX ecosystem, not end users of the devfolio CLI.

Installation

go install github.com/plexusone/devfolio/cmd/devfolio@v0.2.0

Dependencies

  • Add github.com/plexusone/dashforge v0.3.0 (dashboard-IR types)
  • Add github.com/plexusone/omnidevx-core v0.2.0 (event store, period reports, identity resolution)
  • Routine bumps: go-github v88.0.0, gogithub v0.13.0, mogo v0.74.6, structured-changelog v0.14.1

Migration

No breaking changes from v0.1.0. devx dashboard and the contributor profile flags (--api-only, --local-path, --dashboard) are purely additive.

What's Next

Per the OmniDevX ecosystem plan, Phase 6 continues with devfolio collect/aggregate commands and contributor.Profile gaining an AISpace summary sourced from period reports, once the SPACE/DORA analytics engines land in omnidevx-core. Team velocity staying on its current changelog-based implementation until Phase 9, when it's rebased onto rollups of individual period reports.

See CHANGELOG.md for the categorized commit list.