Skip to main content

​
Overview

Blocks can automatically implement features and fix bugs by being assigned to Linear or GitHub issues. This enables autonomous development where agents work on tickets from start to finish, creating pull requests ready for review.

​
How It Works

When you assign @blocks to an issue, it will:
  1. Analyze Requirements: Review the issue description, acceptance criteria, and linked resources
  2. Gather Context: Examine relevant code, dependencies, and related issues
  3. Plan Implementation: Create an approach that aligns with your codebase patterns
  4. Write Code: Implement the feature or fix following best practices
  5. Create PR: Open a pull request with the changes ready for review

​
Using Ticket Assignment

​
Assign via Linear

There are two ways to assign a Linear ticket to Blocks: 1. Native Assignment: Assign the ticket directly to Blocks using Linear’s assignee field. Blocks will automatically start working on it. 2. Mention in Comment: Mention Blocks in a comment with specific instructions: 
@blocks implement this ticket and create a PR

@blocks /plan implement this with a focus on performance
Tip: You can configure the default behavior for native assignments in Settings > Integrations > Linear. Set the default assign mode to “plan” to have Blocks create implementation plans first, allowing you to review and refine the approach before code is written.

​
With Specific Requirements

Provide additional context or constraints: 
@blocks implement this using the existing authentication pattern

@blocks fix this issue without changing the public API

​
What Gets Created

When Blocks completes a ticket assignment, you’ll receive:
  • Pull Request: A new PR with all necessary code changes
  • Tests: Unit and integration tests for new functionality
  • Documentation: Updated README, comments, and inline documentation
  • Commit Messages: Clear, descriptive commit history
  • PR Description: Summary of changes and how to test

​
Best Practices

  • Clear Requirements: Write detailed acceptance criteria and provide examples
  • Link Resources: Reference related issues, PRs, or documentation
  • Use Plan Mode: For complex features, start with /plan to collaborate on the approach
  • Review Thoroughly: Always review generated code before merging
  • Provide Feedback: Give Blocks feedback on implementations to improve future results

​
Plan Mode for Complex Tickets

For larger features or architectural changes, use Plan Mode to collaborate on the implementation strategy before code is written: 
@blocks /plan implement user authentication with OAuth
This allows you to review and refine the approach before implementation begins. Learn more about Plan Mode.

​
Integration Setup

Ticket Assignment works with both Linear and GitHub integrations. Ensure Blocks has access to your project and repositories.

​
Learn More