buildrtech
@buildrtech Organization
Public Skills
scout-api
by buildrtech
Query Scout APM performance data via REST API. Use when investigating app performance, slow endpoints, error groups, traces, or insights like N+1 queries and memory bloat.
ast-grep
by buildrtech
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for code patterns, find specific language constructs, or locate code with particular structural characteristics.
branch-quiz
by buildrtech
"Use when the user wants to verify their understanding of a branch's code changes by being quizzed on runtime behavior, assumptions, failure points, and edge cases instead of just reading diffs"
mcporter
by buildrtech
Interact with MCP (Model Context Protocol) servers using the mcporter CLI. Use this skill when you need to list available MCP servers, view tool schemas, call MCP tools, manage OAuth authentication, or generate CLI wrappers and TypeScript types for MCP servers.
linear
by buildrtech
Use when querying, creating, updating, or managing Linear issues, projects, teams, and initiatives. Auto-invoke when the user mentions Linear tickets, issue tracking, or task management.
fetch-ci-build
by buildrtech
Fetch CI build results and diagnose failures. Auto-detects provider from project files or URLs. Supports GitHub Actions, Buildkite, and CircleCI.
sentry-issue
by buildrtech
Use when given a Sentry issue URL and you need to fetch exception details, stacktrace, and request context using sentry-cli (and Sentry API fallback when needed).
brainstorming
by buildrtech
"You use this before creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation."
executing-plans
by buildrtech
Use when you have a written implementation plan to execute
requesting-code-review
by buildrtech
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
test-driven-development
by buildrtech
Use when implementing any feature or bugfix, before writing implementation code
dispatching-parallel-agents
by buildrtech
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
systematic-debugging
by buildrtech
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
verification-before-completion
by buildrtech
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
writing-plans
by buildrtech
Use when you have a spec or requirements for a multi-step task, before touching code
semantic-commit
by buildrtech
Create semantic git commits following Conventional Commits specification. Use when committing changes, making commits, or when asked to commit.