Menu
Skills in this repository
SkillsMP has collected 62 skills from TudeOrangBiasa/opencode-workflow. Open a skill to review its source and details.
TudeOrangBiasa/opencode-workflowShowing 22 of 62 collected skills.
Use when gitHub operations — issue triage, PR management, CI/CD debugging, release management, and security monitoring via gh CLI. Use only when managing GitHub issues, PRs, CI status, releases, contributors, stale items, or security alerts.
Use when audit the opencode-workflow state — read opencode.json, verify symlinks, check repo sync, analyze recent sessions, surface mismatches. Use when user says audit, workflow status, check changes, verify sync, what did I change, opencode config status,…
Compact the conversation into a handoff document for another agent. Use when user says handoff, hand off, transfer context, pass to another agent, context compaction.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase…
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed. Use when the user wants to create a spec or PRD from current context.
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs. Use when the user wants to triage an issue or PR, review incoming bugs or feature requests, or prepare issues for an AFK…
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
Create, audit, and write great agent skills — structure, progressive disclosure, bundled resources, and the principles that make a skill predictable. Use when user wants to create, write, build, or improve a skill, or asks about skill structure or quality.
Use when regression testing for AI-assisted development — sandbox-mode API testing without DB, automated bug-check workflows, and patterns for AI blind spots where same model writes and reviews code. Use only when AI agents have modified API routes, after bug…
Use when trace every user-facing button through its full state change sequence to find bugs where functions individually work but cancel each other out. Use only when systematic debugging found no bugs but users report broken UI, or after refactors touching…
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Use when error-handling review checklist for typed errors, retry boundaries, user-safe messages, logging, API error envelopes, and swallowed exceptions. Use only when error paths are the task focus or code is at a high-risk boundary.
Use when local-evidence production readiness audit — security, data integrity, operations, payments, UX. Score + blockers + next action. Use only for explicit launch/ship/prod readiness questions, not ordinary review.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Team-ready handoff checklist for changes, verification evidence, version bump decisions, changelog entries, migration notes, rollback notes, and next-owner actions. Use when preparing work for teammates, AFK handoff, release notes, changelog updates, version…
Use when security checklist for Solidity AMM contracts — reentrancy, CEI ordering, donation/inflation attacks, oracle manipulation, slippage, admin controls, and safe reserve math. Use only when writing or auditing AMM, LP vault, or swap contracts.
Use when prevent silent decimal mismatch bugs across EVM chains — runtime decimal lookup, chain-aware caching, bridged-token precision drift, and safe normalization. Use only when reading ERC-20 balances, calculating fiat values, or comparing amounts across…
Use only when computing Ethereum hashes in JavaScript/TypeScript — Node's sha3-256 is NIST SHA3, not Ethereum Keccak-256, and silently breaks selectors, signatures, and storage slots.
Use when review prediction-market, basket, oracle, and trading-agent workflows for compliance, safety, data quality, privacy, and execution risk. Use only before any workflow handles venue auth, user portfolio data, API keys, or trade planning.
Use only when auditing web applications for security bounties — recon, XSS/CSRF/SQLi/SSRF testing, authentication bypasses, and report writing. Not for production security hardening.
Use when security review checklist for diffs touching auth, authorization, input handling, secrets, uploads, payments, PII, dependencies, CORS, or unsafe HTML. Use only when security-sensitive code or configuration changed.
Use when persist agent memory across sessions — store, retrieve, find, or update long-term context. Use when user says memory, remember, openviking, store, retrieve, save context, find memory, search memory. Persistent memory for AI agents with namespace…