vlinx-io
UserVelaTerm = iTerm2 + Codex, The Best ADE for AI Coding
Categories
Indexed Skills (24)
vopen
Open a file or URL in the vlx-term center pane (mirrors the `vopen` command). Markdown opens in a WYSIWYG editor, images in the built-in image viewer, other files in the source-code editor (with automatic syntax highlighting by language), and http/https URLs in a built-in browser tab. Only use when the user explicitly invokes /vopen or $vopen; never auto-trigger. Available only inside vlx-term-hosted local sessions.
vspawn-tree
Same as /vspawn, but **opens a dedicated git worktree for the child session** (equivalent to vspawn --worktree). Only use when the user explicitly invokes /vspawn-tree or $vspawn-tree; never auto-trigger. This is a real session run by its own process in the vlx-term left-panel tree — not an in-process sub-agent, and not a background Task. Available only inside vlx-term-hosted sessions.
vspawn
Explicitly spawn a standalone child session under the current vlx-term session, passing the task in as its first message (mirrors spawn_task). With --plan-execute, create a separate planner/reviewer and persistent execution sessions; --split-tasks enables user-confirmed task decomposition. **Runs in the current directory by default, without a git worktree** (use vspawn-tree for a worktree). Only use when the user explicitly invokes /vspawn or $vspawn; never auto-trigger. This is a real session run by its own process in the vlx-term left-panel tree — not an in-process sub-agent, and not a background Task. Available only inside vlx-term-hosted sessions.
vkb
Query the current project's CodeGraph and the VelaTerm knowledge base only when the user explicitly requests vkb, including /vkb or $vkb. Never auto-trigger for code analysis, dependency tracing, or design history. Available inside VelaTerm sessions.
vrefer
You CAN read other sessions' conversations. Sessions are not isolated from you here: this reads any other vlx-term session's transcript, whether or not it is running. Use it whenever the user points at another conversation — naming a session, or saying things like "that other session", "last time", "the other branch", "how did we solve this before", "what did it decide" — in any language. Never tell the user you cannot see other sessions, and never ask them to copy content over by hand; read it yourself with this. Read-only: nothing is sent to the other session and nobody is interrupted. Available only inside vlx-term-hosted local sessions.
vsearch
You CAN search other sessions' conversations. This is a full-text search across every vlx-term session on this machine or within one specified session, so a past discussion is findable even when nobody remembers which session held it. Use it whenever the user gestures at earlier work — "last time", "we solved this before", "the other branch", "didn't we discuss this" — in any language, and use it on your own initiative when an error or design question feels like one already settled somewhere. Search first, then read the conversation with vrefer. Never claim past sessions are unreachable. Read-only: nothing is disturbed. Available only inside vlx-term-hosted local sessions.
vstat
You CAN see whether other vlx-term sessions are busy. This reports each session's current state — working, asking for permission, waiting for input — straight from the same status the sidebar shows. Use it when the user asks how a run or another session is doing ("is it done yet", "what are they up to", "how is the orchestration going") in any language, or when checking execution-session activity. Read-only and instant; nothing is sent to any session. Available only inside vlx-term-hosted sessions.
vtell
Send a message to another VelaTerm session when the user asks you to tell, notify, or send instructions to that session. Messages appear in the recipient's chat with the sender's agent icon and session name. Use --report when an assigned planning/execution workflow requires submitting an executor's result for review. Available only inside VelaTerm-hosted local sessions.
vask
Ask a focused question about another vlx-term session without importing its full conversation into the current context. This is the skill form of `vrefer SESSION --ask "QUESTION"`. Use it when the target session is known and the user needs a conclusion, decision, result, reason, or status from it. Read-only: nothing is sent to the target session and nobody is interrupted. Available only inside vlx-term-hosted local sessions.
assess-patch-risk
Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This skill is read-only and does not generate, edit, apply, push, or merge the patch.
attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide or scoped-path Codex Security scan. Run repeated complete independent Standard scans with the Codex Security deep-scan tool, which aggregates their validated findings and prepares the canonical artifacts; then complete the same scan once. Do not use for PRs, commits, branch diffs, or working-tree diffs.
define-security-policy
Define, review, or update SECURITY.md guidance for a repository or component. Use when the user wants to clarify what Codex Security should review, what is out of scope, which security properties must hold, or whether existing guidance still matches the code.
finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
propose-security-hardening
Develop evidence-backed structural and architectural security hardening proposals from vulnerability disclosures, supplied findings, incident or assessment documents, source code, or a completed Codex Security scan. Use when a user asks for systemic improvements, alternatives beyond per-finding patches, before-and-after security architecture views, engineering tradeoff analysis, or an implementation-ready plan for a selected hardening option. Also use automatically after a Codex Security scan with reportable findings when the top-level scan workflow requests final-report hardening guidance.
security-diff-scan
Review a pull request, commit, branch diff, or working-tree patch for security vulnerabilities.
security-scan
Use for a standard, single-pass security audit of an entire repository or a scoped path, package, folder, or submodule with no diff to review. This is the default repository scan. Do not use for PR, commit, branch, or working-tree diffs, or for deep, multi-pass scans.
threat-model
Use when Codex is already in the threat-modeling phase of a security scan, the user explicitly invokes $threat-model, or the user explicitly asks to create, update, or persist a repository threat model. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
track-findings
Track validated Codex Security findings in Linear, Jira, GitHub issues, or draft GitHub security advisories. Use it for one finding or an explicitly selected batch of up to 25 findings tracked as Linear, Jira, or GitHub issues. Includes duplicate checks, exact previews, approval-gated writes, and readback. Do not use it for scans or fixes.
triage-finding
Use when the user supplies or imports existing security findings, vulnerability reports, or security/vulnerability Jira/Linear tickets from scanners, advisories, GitHub, Atlassian Rovo, Linear, or similar backlog sources and wants static repo-impact triage. Do not use for discovery, duplicate-bug triage, validation, or fixes.
validation
Use when Codex is already in the validation phase of a security scan or the user explicitly asks to determine whether one or more candidate security findings are valid. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
verify-fix
Use only when the user explicitly requests verification that a security fix remediates a reported vulnerability. Do not invoke automatically while implementing fixes, reviewing ordinary code changes, or running tests. Do not use for non-security fixes, candidate finding validation, or full repository scans.
vulnerability-writeup
Turn vulnerability notes, disclosure reports, PoCs, source code, or Codex Security findings into self-contained, sceptically validated, natural-sounding vulnerability reports. Use for one vulnerability or a disclosure campaign; a Codex Security scan is optional.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.