From gitee-toolkit
Use this skill when the user wants to get quick fix suggestions for an issue, "how to fix this issue", "where should I make changes", "quick-fix-suggestion", "suggest fix", "fix suggestion", "how to implement this issue", or before starting implementation to understand the scope of changes. This skill analyzes the issue content, locates relevant code in the repository, and suggests which files to modify with draft implementation plans. Requires Gitee MCP Server to be configured and must be run in a local git repository.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gitee-toolkit:quick-fix-suggestionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Note**: If you have `mcporter` installed locally, you should use `mcporter` to invoke the MCP tool instead of directly calling the MCP tool. The `mcporter` CLI provides a more convenient interface and better error handling.
Note: If you have
mcporterinstalled locally, you should usemcporterto invoke the MCP tool instead of directly calling the MCP tool. ThemcporterCLI provides a more convenient interface and better error handling.
Analyze a Gitee Issue and generate intelligent fix suggestions including:
get_repo_issue_detail, list_issue_comments, search_files_by_content, get_file_content)Why Local-First?
This skill prioritizes local file operations over Gitee API for code search:
- Speed: Local searches complete in milliseconds vs. seconds for API calls
- No Rate Limits: No 100 requests/minute restriction
- Real-time: Searches include uncommitted local changes
- Cost: Zero API usage costs
| Priority | Tool | Availability |
|---|---|---|
| 1st | glob, grep (built-in) | 100% |
| 2nd | ast_grep_search, lsp_find_references | 100% |
| 3rd | Git commands (via bash) | ~90% |
| Last | Gitee API (search_files_by_content) | Fallback only |
Use get_repo_issue_detail to retrieve full Issue information:
Identify Issue Type:
bug: error, crash, broken, not working, 错误, 失败feature: add, support, implement, new, 新增, 添加enhancement: improve, optimize, 改进, 优化Extract Code Entities:
Use built-in tools in priority order:
// 1. File name search (fastest)
glob(`**/*${keyword}*.{js,ts,py,go}`, { cwd: localRepoPath })
// 2. Content search
grep({
pattern: `function\\s+${funcName}`,
path: localRepoPath,
output_mode: "content"
})
// 3. AST search (semantic)
ast_grep_search({
pattern: "function $NAME($$$) { $$$ }",
lang: "javascript",
paths: [localRepoPath]
})
// 4. Fallback: Remote search (max 3 calls)
if (localResults.length < 3) {
search_files_by_content({ owner, repo, query: keyword, limit: 10 })
}
Read each candidate file to:
Present results in this format:
## Issue #{number}: {title}
**Type**: {bug/feature} | **Confidence**: {score}% | **Complexity**: {low/medium/high}
### Primary Files (Must Modify)
**1. `{file_path}`** [Confidence: XX%]
- **Change**: {modify/add/delete}
- **Location**: Around line {X}
<details>
<summary>Code Draft</summary>
```{language}
// Current:
{existing_code}
// Suggested:
{suggested_code}
{file_path}: {reason}{file}, ~{time}{file}, ~{time}
### Step 6: Handle User Response
- **Approve**: Summarize and transition to `implement-issue` skill
- **Adjust**: Re-analyze with new information
- **Search More**: Expand search scope
- **Cancel**: Offer other help
## Notes
- Always indicate confidence level - ask for clarification when uncertain
- Follow existing code patterns when suggesting changes
- Warn immediately if Issue mentions credentials/secrets
- If unable to locate relevant code, ask for more context rather than guessing
## References
- [Tool Reference Guide](references/TOOL_REFERENCE.md) - Detailed search patterns and tool usage
npx claudepluginhub chy5301/cc-plugins --plugin gitee-toolkitInvestigates and resolves GitHub issues with systematic triage, root cause analysis, test-driven fixes, and pull request management. Use when given an issue ID or URL.
Fixes GitHub issues end-to-end with GitHub CLI: views issue, researches context, plans fix, creates branch, implements/tests changes, submits PR.
Resolves GitHub issues via 8-phase workflow: fetch details, analyze requirements, implement solutions, verify correctness, code review, commit changes, create PRs. Activates on resolve, implement, fix requests or issue references.