mirror of
https://github.com/IgorWarzocha/Opencode-Workflows.git
synced 2026-09-14 16:22:53 +08:00
OpenCode Agent
2698a1d765
- Implement internal maintenance suite: repo-maintainer agent and automated audit/sync scripts. - Add "Opencode Configurator" suite: agent-architect, command-creator, and skill-creator. - Refactor core commands (/improve, /refactor, /rmslop) to RFC 2119 + XML standards. - Standardize all agent metadata and structural tagging across the repository. - Introduce utility commands: /npm for package management and /create-pack for bundling. - Overhaul README.md and documentation to reflect new workflow patterns.
1.1 KiB
1.1 KiB
Output Patterns
<template_pattern>
Template Outputs
Strict format (for API responses, data formats):
ALWAYS use this structure:
# [Title]
## Executive summary
[One paragraph]
## Key findings
- Finding 1
- Finding 2
## Recommendations
1. Action 1
2. Action 2
- MUST use exact structure for strict templates
- MUST NOT deviate from specified headings
Flexible format (when adaptation useful):
Default format (adjust as needed):
# [Title]
## Summary
## Findings
## Recommendations
- SHOULD follow default structure
- MAY adjust based on content needs
</template_pattern>
<examples_pattern>
Example-Based Outputs
Show input/output pairs when output style matters:
**Example 1:**
Input: Added user auth with JWT
Output:
feat(auth): implement JWT authentication
Add login endpoint and token middleware
**Example 2:**
Input: Fixed date display bug
Output:
fix(reports): correct date timezone conversion
- SHOULD use examples over descriptions for style guidance
- SHOULD include 2-3 examples covering different cases
</examples_pattern>