π·πΊ Π ΡΡΡΠΊΠ°Ρ Π²Π΅ΡΡΠΈΡ β README.ru.md
Solo developer's portfolio cockpit. Bugs, requirements, deploy β all in markdown.
Managing 10 GitHub repos as one person hits friction GitHub itself doesn't solve: bugs scattered across per-repo Issues, no portfolio-wide overview, multi-repo features (client + server + microservice) demand mental coordination, deploy automation gets hand-rolled in every new project. And the moment you delegate a bug fix to an AI agent, "the agent said it's done, I forgot to verify" silently becomes the failure mode.
Solo Dev Hub is a single-window desktop app that organizes your portfolio, locks every bug into a verifiable AI-agent workflow, tracks tasks in commit-able Markdown, syncs requirements between repos, and bundles deploy automation β all under one roof.
Built for solo developers, indie hackers, and freelancers running 5+ active GitHub repos who don't want to:
AI-ready by design. Bugs, tasks, requirements, project metadata, and CLAUDE.md sections all live as Markdown inside your repos. Every AI assistant (Claude, ChatGPT, Copilot) reads your entire portfolio context without an API integration β git clone is the integration.
created β in-progress β testing β confirmed / rejected) splits roles cleanly: the AI agent takes a bug, applies a fix, moves it to testing with a comment describing what it did; you verify and click β or β. The agent cannot edit description, severity, category, or fix_attempts β only status and comment are AI-writable. The attempt counter auto-increments on every testing transition, so "how many tries did this take" is honest history, not a self-report. Net effect: no bug falls through the gap between "agent said it's fixed" and "I forgot to check".docs/bug-reports.md of the affected repo. SQLite is the source-of-truth, the MD file is a 2-way-synced LLM-readable view. Severity, category, append-only event log per bug.REQ-NNN.md exchange between client β server β microservice. Sender writes the ask, recipient writes the receipt, the app handles file movement between repos. No GitHub Issues, no email threads..gitignore, deploy YAML, CLAUDE.md sections. Customize once in the app, sync into every project..env, never a plaintext file.rusqlite, file I/O for sync, Windows Credential Manager via keyring@octokit/rest (called directly from the JS side, never proxied through Rust)tauri-plugin-updater with Ed25519 signing; production builds via GitHub Actions on v* tag pushCurrent builds are Windows x64 only. Tauri supports macOS and Linux architecturally; non-Windows builds may appear in the release pipeline by request.
solo-dev-hub_<version>_x64-setup.exe from the Releases pagerepo β full repository access (read your repos, manage Actions secrets)workflow β required for the deploy automationread:user β read your profile infoC:\Users\You\Development\).docs/bug-reports.md (the MD is a view; SQLite is the SoT).npm install
npm run tauri dev # local dev with hot reload
cd src-tauri && cargo test --lib # ~370 Rust tests
npm test # vitest frontend (~70 tests)
npm run check # svelte-check
Production releases are built by GitHub Actions on v* tag push β never build locally for distribution (unsigned, no latest.json):
git tag -a vX.Y.Z -m "vX.Y.Z"
git push origin master vX.Y.Z
The full release runbook (key rotation, CI troubleshooting, hotfix flow) β docs/RELEASING.md.
CLAUDE.md (gitignored) carries the in-project AI rules. The app's "Sync to ~/.claude/CLAUDE.md" feature pushes the global section into your user-level Claude Code config. Per-project CLAUDE.md sits in each repo's root.
lib.rs / tauri-commands.ts splits, decomposing the 570-line sync_project handler), docs/ARCHITECTURE.md for contributors, SQLite ER-graph, in-app multilingual help screen.## Status: frontmatter.Full backlog and per-version task lists β docs/roadmap.md.
The app is free and ad-free. If it saves you time, consider supporting development:
UQA-0I3SN2vw8F2ZzEoOTXT36-ToF0mu4Yp4_6pVmsR_dI0SOr use the in-app About screen β one-click links and copy-to-clipboard for the TON address.
MIT Β© 2026 Sgonnov D.A.