OpenCode使用指南

---description: create git commitsubtask: true---Follow these steps to generate and execute a commit:1. **Analyze changes**: Run `git --no-pager diff --cached` to examine the staged modifications.2. **Generate message**: Create a conventional commit message based on the changes using the format:   - Determine type: `feat` , `fix` , `docs` , `style` , `refactor` , `test` , `chore`   - Add optional scope in parentheses if applicable, for example, `doc(api)`   - Write concise description (50 chars max)   - Add body if explanation needed, separated by blank line, prefer to explain WHY something was done from an end user perspective instead of WHAT was done.   - The output language should be English if not specified otherwise.1. **Execute commit**: Run `git commit -m "generated message"`

---mode: primaryhidden: truemodel: opencode/claude-haiku-4-5color: "#E67E22"tools:  "*": false  "github-pr-search": true---You are a duplicate PR detection agent. When a PR is opened, your job is to search for potentially duplicate or related open PRs.Use the github-pr-search tool to search for PRs that might be addressing the same issue or feature.IMPORTANT: The input will contain a line `CURRENT_PR_NUMBER: NNNN`. This is the current PR number, you should not mark that the current PR as a duplicate of itself.Search using keywords from the PR title and description. Try multiple searches with different relevant terms.If you find potential duplicates:- List them with their titles and URLs- Briefly explain why they might be relatedIf no duplicates are found, say so clearly. BUT ONLY SAY "No duplicate PRs found" (don't say anything else if no dups)Keep your response concise and actionable.

~/.config/opencode/skills/skill-creator├── LICENSE.txt├── references  # 在SKILLS.md中引用的参考文档│   ├── output-patterns.md│   └── workflows.md├── scripts # 在SKILLS.md中引用的脚本│   ├── init_skill.py│   ├── package_skill.py│   └── quick_validate.py└── SKILL.md

---name: git-releasedescription: Create consistent releases and changelogslicense: MITcompatibility: opencodemetadata:  audience: maintainers  workflow: github---content

---name: markdown-codeblockdescription: Use when the user wants to highlight code in markdown files, including inline code highlighting with {lang} prefix syntax, code blocks with language fences and titles, and transformer marks for diffs, highlights, focus, errors, and warnings. Always read this skill file when inserting code blocks or inline code in markdown.---# Shiki Code Highlighting for Markdown Blogs## Inline Code SyntaxApply to code wrapped in **single backticks**:```md`{python} print("Hello")``{javascript} console.log("x")``{html} <div></div>``{rust} fn main() {}``{shell} echo "hi"````**Do NOT** use `{lang}` prefix on triple-backtick code blocks.## Code BlocksUse language name in opening fence. Optionally add filename after language:```pythondef greet(name):    return f"Hello, {name}!"``````typescript hello.tsconst add = (a: number, b: number): number => a + b;```### Nested Code BlocksThe default number of backticks for code blocks is 3. When there are nested code blocks inside the content, the outer code block's backticks increase by one per nesting level. If there are multiple layers of nesting, continue adding backticks accordingly.For example, if the inner content contains triple backticks, use 4 backticks for the outer wrapper:````md```typescript// Your code example here that might contain ``` in it```````If the inner content has 4 backticks, use 5 for the outer, and so on.## Transformer MarksAdd marks in comments after `#`. Use marks to draw attention or add semantic meaning:| Mark                  | When to Use                                         || --------------------- | --------------------------------------------------- || `# [!code --]`        | Show code removal (before → after comparisons)      || `# [!code ++]`        | Show code addition (before → after comparisons)     || `# [!code highlight]` | Emphasize important or key lines                    || `# [!code word:term]` | Highlight specific identifier, keyword, or term     || `# [!code focus]`     | De-emphasize surrounding code, focus on one section || `# [!code error]`     | Mark lines with errors, invalid code, or exceptions || `# [!code warning]`   | Mark lines with warnings, deprecations, or cautions |### Examples```rustlet x = 5; // [!code --]let x = 10; // [!code ++]```Word Highlight```typescript// [!code word:interface]interface User {  id: number;  // [!code word:id]  name: string;  // [!code word:name]}```