skills.rest
quan2005
quan2005COMMUNITY
Explore all skills by this author →
GitHub

opencode-subagent

Dispatch an isolated opencode CLI subagent to verify repository work and write a report.

13|2|Updated Mar 13, 2026
Search Tags:#verification#report generation#subagent#opencode#cli automation#requirements review#repository workflow
One-click install
npx skills add https://github.com/quan2005/journal-claw --skill opencode-subagent
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opencode-subagent
Source: https://github.com/quan2005/journal-claw/tree/main/.agents/skills/opencode-subagent
Command: npx skills add https://github.com/quan2005/journal-claw --skill opencode-subagent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you delegate repository verification work to an independent, headless subagent without losing control of scope, output format, or auditability. It is useful when a task needs context isolation, a written report on disk, and a repeatable invocation pattern instead of ad hoc prompting.

Core Features & Use Cases

  • Standardized subagent execution: Wraps opencode run with a fixed call pattern, enforced primary agent selection, and prompt-file based execution.
  • Verification-focused reporting: Produces a repository-local report file that checks story and optional design requirements against a specified file scope, then ends with a strict SUMMARY line.
  • Safety guardrails: Blocks unsafe output paths like /tmp for final reports, rejects empty or incorrect scope usage, and discourages permission-bypass flags or fabricated success states.
  • Use cases: Ideal for verification-gate reviews, requirements-gate follow-ups, and documentation maintenance tasks where the main agent needs an external, auditable subagent result.

Quick Start

Ask the AI to use the opencode-subagent skill to verify a story and optional design against specific repository files and write the report to a markdown file inside the repo.

Frequently Asked Questions about opencode-subagent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate repository verification against story requirements using a subagent?▼

Automating repository verification involves dispatching an isolated opencode CLI subagent to check work against story and optional design contracts, generating an auditable report file. It enforces context isolation, fixed file scope validation, and a SUMMARY line for deterministic downstream review.

What is the best way to generate auditable repository reports with fixed file scope?▼

Generating auditable repository reports requires a standardized subagent execution pattern that wraps opencode run with a fixed call pattern. It produces a repository-local markdown file verifying specific file scopes against requirements, ending with a strict SUMMARY line for deterministic downstream review.

Does opencode subagent execution support context isolation for requirements-gate reviews?▼

Opencode subagent execution supports context isolation for requirements-gate reviews by running headless subagents with fixed file scopes. It enforces prompt-file based execution and repository-local output paths, rejecting unsafe directories like /tmp for final reports.

How do I enforce safe output paths when running CLI automation for report generation?▼

Enforcing safe output paths during CLI automation requires safety guardrails that block unsafe directories like /tmp for final reports. The subagent execution pattern rejects empty or incorrect scope usage, discourages permission-bypass flags, and mandates reports saved inside the repository.

When should I use an isolated subagent for documentation maintenance tasks?▼

You should use an isolated subagent for documentation maintenance tasks when you need context isolation and auditable output saved inside the repository. It is ideal when the main agent requires an external, repeatable verification result rather than ad hoc prompting.

Why does my subagent verification report fail deterministic downstream review?▼

Subagent verification reports fail deterministic downstream review when missing the mandatory SUMMARY line. The opencode-subagent pattern enforces prompt-file execution, scope validation, and this strict SUMMARY line to ensure automated reviews process the auditable output correctly.

Related Skills

Explore More Software Engineering Skills→
jal-cojal-co
7

opencode-agents

Define and configure OpenCD agents with permissions, tools, and mode settings.

Community
Advanced
maslennikov-igmaslennikov-ig
243

parse-error-logs

Parse npm, pnpm, TypeScript, Jest, and build logs into structured JSON reports.

Community
Intermediate
nicobailonnicobailon
561

interactive-shell

Control and supervise interactive CLI sessions via overlay or headless dispatch.

Community
Advanced
curiositechcuriositech
2

dag-runtime

Execute DAG workflows with concurrent agent isolation, permissions, retries, and execution tracing.

Official
Advanced