> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blocks.team/llms.txt
> Use this file to discover all available pages before exploring further.

# Question Answering

## Overview

You can ask Blocks questions about your codebase — how things work, where code lives, why changes were made — directly in Slack, Linear, GitHub, or the Blocks dashboard.

If Blocks can't find an answer in your codebase, it will say so rather than guessing.

## 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

**Slack** — Mention `@blocks` in any channel, or DM the Blocks app directly for private questions.

**Linear** — Ask in issue comments to get context while you work: `@blocks` is there existing code we can reuse for this feature?

**GitHub** — Comment on issues or PRs: `@blocks` what tests exist for this module?

**GitLab** — Comment on issues or merge requests: `@blocks` what tests exist for this module?

**Bitbucket** — Comment on issues or PRs: `@blocks` what tests exist for this module?

**Dashboard** — Use the Blocks dashboard as a chat interface for open-ended exploration, especially when you're not sure yet what to ask.

## Getting References

Blocks doesn't include file links by default, but you can ask for them:

* `@blocks` where is the payment processing logic — include file links

## 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](/using-blocks/features/multi-repo-support).