Skip to main content

​
Overview

Blocks can answer technical questions about your codebase, infrastructure, and development processes. This helps team members quickly find information without digging through documentation or asking colleagues, accelerating development and reducing context-switching.

​
How It Works

When you ask Blocks a question, it will:
  1. Understand the Query: Parse your question to identify what information you need
  2. Search Codebase: Scan relevant files, documentation, and commit history
  3. Analyze Context: Connect related pieces of information across your repositories
  4. Generate Answer: Provide a clear, detailed response with code examples and references
  5. Cite Sources: Link to specific files, line numbers, and documentation

​
Using Question Answering

​
Code Questions

Ask about how specific functionality works: 
@blocks how does user authentication work in our app?

@blocks where is the payment processing logic implemented?

@blocks what's the difference between UserService and AuthService?

​
Architecture Questions

Get insights about system design: 
@blocks explain the microservices architecture in our backend

@blocks how do we handle database migrations?

@blocks what's our caching strategy?

​
API Questions

Learn about endpoints and integrations: 
@blocks list all POST endpoints in the API

@blocks how do we integrate with Stripe?

@blocks what external services does our app depend on?

​
Historical Questions

Understand why changes were made: 
@blocks why was the authentication flow refactored?

@blocks what was changed in the last deployment?

@blocks show me recent changes to the user model

​
Where to Ask Questions

​
Slack

Mention @blocks in any Slack channel: 
@blocks how do we handle errors in the API layer?

​
Linear

Ask questions in Linear issue comments: 
@blocks is there existing code we can reuse for this feature?

​
GitHub

Comment on issues or PRs: 
@blocks what tests exist for this module?

​
Dashboard

Use the Blocks dashboard for private questions or exploratory research.

​
What Blocks Can Answer

  • Implementation Details: How specific features work under the hood
  • Best Practices: Your team’s conventions and patterns
  • Dependencies: What libraries and services you use
  • Code Location: Where to find specific functionality
  • Change History: What changed and why
  • Configuration: Environment setup and deployment processes
  • Testing: What tests exist and how to run them

​
Best Practices

  • Be Specific: Include relevant context like module names or feature areas
  • Ask Follow-ups: Continue the conversation to drill deeper into topics
  • Request Examples: Ask for code examples to see patterns in action
  • Verify Answers: Cross-reference important information with your team
  • Share Knowledge: Document frequently asked questions in your team wiki

​
Multi-Repo Support

Blocks can answer questions that span multiple repositories: 
@blocks how does the frontend communicate with the backend API?

@blocks compare the authentication implementation in our web and mobile apps
Learn more about Multi-Repo Support.

​
Integration Setup

Question Answering works across all Blocks integrations:
  • Slack - Ask questions in team channels
  • Linear - Get context while working on issues
  • GitHub - Answer questions in code reviews

​
Learn More