Use concrete JSON and Markdown examples to structure Sergo tool caches, strategy histories, improvement tasks, and reports. The templates show which fields to record and how to organize findings for review.
中文简介正在准备中。当前显示英语简介。
Optional Sergo examples for cache formats and reporting templates.
安装前可以查看交给 AI 代理的指令内容。
Use this skill only when Sergo needs concrete format examples.
{
"last_updated": "2026-01-15T12:00:00Z",
"tools": [
{"name": "tool-name-1", "description": "..."},
{"name": "tool-name-2", "description": "..."}
]
}
{"date": "2026-01-14", "strategy": "symbol-analysis", "tools": ["find-symbol", "get-definition"], "findings": 3, "tasks_created": 2, "success_score": 8}
{"date": "2026-01-13", "strategy": "type-inspection", "tools": ["get-hover", "get-type"], "findings": 5, "tasks_created": 3, "success_score": 9}
### Task [N]: [Short Title]
**Issue Type**: [Symbol Analysis / Type Inspection / etc.]
**Problem**: [Clear description]
**Location(s)**: [file paths and line references]
**Impact**: Severity, affected files, risk
**Recommendation**: [Specific fix]
**Validation**: Existing tests, Serena verification, related-pattern check, docs if needed
**Estimated Effort**: [Small/Medium/Large]
Follow the reporting skill (headers ###+, <details> for long sections):
### 🔬 Sergo Report: [Strategy Name]
**Date**: [YYYY-MM-DD]
**Strategy**: [Name]
**Success Score**: [X/10]
### Executive Summary
### 🛠️ Serena Tools Update
### 📊 Strategy Selection
### 🔍 Analysis Execution
<details>
<summary><b>📋 Detailed Findings</b></summary>
</details>
### ✅ Improvement Tasks Generated
### 📈 Success Metrics
<details>
<summary><b>📊 Historical Context</b></summary>
</details>
### 🎯 Recommendations
### 🔄 Next Run Preview
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.
中文简介正在准备中。当前显示英语简介。
Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.
中文简介正在准备中。当前显示英语简介。
Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.
中文简介正在准备中。当前显示英语简介。
Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.
中文简介正在准备中。当前显示英语简介。
Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.
中文简介正在准备中。当前显示英语简介。
Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.
中文简介正在准备中。当前显示英语简介。