Skip to main content
GitHub repository

vh-solara

vh-solara contains 11 collected skills from vhqtvn, with repository-level occupation coverage and site-owned skill detail pages.

skills collected
11
Stars
8
updated
2026-07-25
Forks
0
Occupation coverage
3 occupation categories · 100% classified
repository explorer

Skills in this repository

harness-operator
software-developers

Operate the vh-solara agent harness itself — install, self-update, run the upgrade loop, read release migration notes, and use guide/update/doctor. Load this skill when asked to install, update, or operate the harness, or to read what changed in a release.

2026-07-25
backlog
computer-occupations-all-other

Backlog ledger discipline for vh-solara — conflict-safe edits to docs/planning/backlog.md (hybrid split-commit) plus DEFER/follow-up curation routing. Load this skill before editing the backlog, when handling a cas_conflict on the backlog, or when deciding where a DEFER/p2 finding should land.

2026-07-22
media-perception
computer-occupations-all-other

Caller-facing routing aid for media-perception in vh-solara — decide between in-context perception (vision-capable caller) and single-delegation to the media-perception specialist (text-only caller or heavy/multi-step perception). Load this skill when you hold an image, diagram, chart, video, document/PDF, or audio locator and need to decide how to perceive it.

2026-07-22
debugging-loop
software-developers

Debugging loop for existing bugs — build a deterministic red signal FIRST, then reproduce, minimise, hypothesise, instrument, fix, regression-test, with a 3-line post-mortem. Use this when fixing a bug, chasing a failure, or reproducing a defect. Includes an explicit downgrade-to-human handoff when deterministic red is unavailable.

2026-07-15
skill-creator
software-developers

Guide for creating and updating repo-local OpenCode skills in this coding repository. Use this whenever a user asks to create, update, improve, validate, or troubleshoot a skill under `.opencode/skills/`, or when archived sessions should be distilled into reusable coding workflows.

2026-07-15
tdd-loop
software-developers

Test-driven development loop for new behavior — red, green, refactor, next vertical slice. Use this when adding or changing behavior test-first at pre-agreed seams. Loads when the user asks to TDD a feature, write tests first, drive an implementation with tests, or settle when refactor should happen.

2026-07-15
gated-commit
software-developers

Gated-commit protocol for vh-solara. Load this skill when you need to commit changes, stage files, or understand the commit-gate enforcement model. Use this whenever the task involves git add, git commit, git push, git reset, or any git write operation.

2026-07-13
think-mode
computer-occupations-all-other

Decision helper for picking the right read-only opencode workflow — researcher, debate, one-shot solution-brief, or phased solution-brief (research.md → debate.md → brief.md) — based on the question's uncertainty shape. Use this when the operator asks "should we research / debate / solution-brief this?", before drafting any new read-only session prompt, when the framing is ambiguous about which workflow shape fits, or when a stakeholder reframe has just landed and the workflow choice should be reconsidered.

2026-07-13
bgshell-job
network-and-computer-systems-administrators

Launch, monitor, stop, list, or resume long-running non-GPU local shell tasks without relying on one shell timeout. Use this when the user asks to run local build/release/maintenance commands that may outlive one shell call or one OpenCode session.

2026-07-08
diagnostics-export
software-developers

Package a safe-to-share bug bundle for vh-solara via `vh-agent-harness diagnostics-export`. Loads when the operator needs to share harness state with a maintainer, file a bug report, or archive session memory for a complex issue. Field-aware secret redaction, repo-local output, never auto-uploaded.

2026-07-08
repo-recon
software-developers

Generator/maintainer for the project's repo-recon structural data file at `.opencode/repo-configs/repo-recon-data.yml`. Use this whenever the user asks to map the repo, locate entrypoints/hotspots/packages/tests, create or refresh the repo-recon data, or recreate it after a structural change. The data file is external_generated — the harness scaffolds it blank on install, then the project (this skill or project agents) owns it.

2026-06-26