golang-best-practices
Provide best practice guidance for Golang project development, including code structure, error handling, concurrency patterns, etc.
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-18 00:15
41,592 results
Provide best practice guidance for Golang project development, including code structure, error handling, concurrency patterns, etc.
Use when building C# applications with .NET 8+, ASP.NET Core APIs, or Blazor web apps. Builds REST APIs using minimal or controller-based routing, configures…
Generate a PR_MESSAGE.md file from session context using GitHub CLI. Detects related issues via branch-keyword search, writes a structured PR description with…
Continue the latest unfinished coding task from the opposite local agent using native Claude Code or Codex session history plus a deterministic snapshot of the…
Orchestrates delivery tracking. Use when you need to decide between daily, status report, or post-implementation report, or when you need guidance on how to…
When a new idea arrives mid-development, classify it, assess destructiveness, audit consumers, and choose the lowest-impact integration path instead of…
Install, configure, and run cabrakan, an OpenAPI-to-MCP server (CLI and TypeScript library). Use when adding cabrakan, turning OpenAPI or Swagger into MCP…
How and when to use the Dodo Payments MCP servers (dodo-knowledge for docs search, dodopayments-api for the live API via Code Mode) safely. Use when looking up…
Use the Azure DevOps REST API to run a health check on a team's requirements-level backlog (Product Backlog Item, User Story, Requirement, Issue) according to Microsoft's Azure Boards best practices: identify missing estimates, missing acceptance criteria, no parent item (Feature/Epic), items in progress but not…
Use the Azure DevOps REST API to retrieve the team's requirements-level backlog (Product Backlog Item, User Story, and Bug), filter for in-progress items assigned to the current user, include parent-child hierarchy, and sort by priority. When the user wants to see their backlog items on the team board, the work they are responsible for, or the Sprint of these items…
Use the Azure DevOps REST API to list work items currently assigned to the current user in a project that are not yet completed, grouped by type, sorted by most recent change, with clickable links. Use when the user wants to see "my work," work items assigned to themselves, or their current to-do list. To query by arbitrary conditions or run a saved query (WIQL), use `boards-query`。
Use the Azure DevOps REST API to get the in-progress backlog items of the entire team, showing dependencies, priority, and Sprint assignment: first list the work that blocks other items, then list high-priority items and items due in this Sprint, along with the parent-child hierarchy, Iteration name, and end date. Use when the user wants to grasp the team's current progress, blockers, or this Sprint's work.
Create and modify work items with the Azure DevOps REST API: create User Stories, Product Backlog Items, Bugs, and Tasks and set parent items, break down a work item into multiple child Tasks, update fields, State, Sprint, and assignee, and add comments. For creation and updates, always first…
List, view, and troubleshoot Pipeline builds with the Azure DevOps REST API: show recent builds for a Pipeline definition, the status and result of a single build, the logs of failed steps, and the changes included in a build. Use when the user asks about the build list, build status, why a build failed, or which commits are included in a build. To trigger a Pipeline, use…
Run Pipelines with the Azure DevOps REST API: trigger YAML or classic Pipelines with a specified branch, runtime parameters (templateParameters), queue-time variables, and stages to skip; for YAML, first use previewRun…
Use the Azure DevOps REST API to audit the branch policies of a repository's default branch, compare against the Microsoft recommended baseline (at least two reviewers, creator's vote does not count, re-approval after push, linked work items, build validation, comments must be resolved), list repositories without any policies, and include the web-portal remediation steps; read-only, no modifications. When the user wants to audit branch protection, check…
Search Azure Repos code and commits with the Azure DevOps REST API: use Code Search syntax (ext:, file:, path:, class:, def:, ref:, AND/OR/NOT) to find code across organizations, projects, or repositories, read a specified branch or commit…
Review Pull Requests (PRs) with the Azure DevOps REST API: list PRs awaiting my review or created by me, summarize a single PR's changed files and diff, discussion threads, reviewer votes, linked work items, and the reasons it is blocked (branch policy), look up a PR from a commit, and, after confirmation, comment, reply, resolve discussions, or vote. When the user wants to...
Create a Pull Request (PR) from the current git branch using the Azure DevOps REST API: draft the title and description based on commits and the PR template, link work items, specify reviewers, or create a draft; and modify your own PR: publish a draft, add reviewers, set or clear…
Read and edit Wiki via the Azure DevOps REST API: list a project's wikis (project wiki and code wiki), browse the page tree, read page content, search Wiki pages by keyword, and after confirmation create a new page, or show a diff first and then update an existing page. When the user wants to look up the Wiki...
Use the Azure DevOps REST API to list and create Iterations (Sprints), and assign Iterations to teams. Use when the user wants to view a project's or team's Iterations, create a new Sprint following an existing cadence, or configure which Iterations a team subscribes to.
Use the LiteLLM Python SDK to build or review completions, streaming, structured outputs, tool calling, the Responses API, and basic cost tracking. Use when the task is to call LiteLLM directly within a Python program rather than managing a Proxy; Proxy, virtual...
Review Spec Kit code changes to confirm they are consistent with applicable design documents, have positive and negative test coverage, bug fixes have regression evidence, and repository terminology is consistent. Use when reviewing diffs or pull requests. Do not use to implement changes or post GitHub review actions.
Guide for adding new CLI commands or subcommands to twist-cli. Use when implementing new SDK endpoints, adding subcommands to existing command groups, or…