بنقرة واحدة
gopls
How to use the gopls MCP for analyzing Go code. Use when working on a Go codebase.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
How to use the gopls MCP for analyzing Go code. Use when working on a Go codebase.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Author a teach workspace's lessons/reference/index in markdown and build both the browsable HTML site and a phone-friendly EPUB from that one source.
A relentless interview that asks every frontier question at once, round by round.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Print the relevant text as raw copy-able markdown and copy it to the clipboard. Run `/markdown file` to copy it as a file reference instead, for pasting into Slack.
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
| name | gopls |
| description | How to use the gopls MCP for analyzing Go code. Use when working on a Go codebase. |
When reading this file please explicitly mention that you did.
You are an AI programming assistant helping users with Go code. You have access to gopls-mcp tools for semantic code analysis.
go_search for text content (comments, strings, TODOs). Use Grep tool.| Task | Tool |
|---|---|
| Find interface implementations | go_implementation |
| Trace call relationships | go_get_call_hierarchy |
| Find symbol references | go_symbol_references |
| Jump to definition | go_definition |
| Analyze dependencies | go_get_dependency_graph |
| Preview renaming | go_dryrun_rename_symbol |
| Task | Tool | Fallback after 3 failures |
|---|---|---|
| List package symbols | go_list_package_symbols | Glob + Read |
| List module packages | go_list_module_packages | find |
| Analyze workspace | go_analyze_workspace | Manual exploration |
| Quick project overview | go_get_started | Read README + go.mod |
| Search symbols by name | go_search | grep + Read |
| Check compilation | go_build_check | go build |
| Get symbol details | go_get_package_symbol_detail | Read |
| List modules | go_list_modules | Read go.mod |
query MUST NOT contain spaces or semantic descriptions.query="ParseInt".symbol_filters format: [{name: "Start", receiver: "*Server"}].receiver requires exact string match ("*Server" != "Server").symbol_name: Do not include package prefix (Use "Start", not "Server.Start").context_file: Obtain strictly from the current file being analyzed.Trigger fallback manually IF AND ONLY IF: