Welcome to Octiew
Welcome to Octiew
We’re excited to introduce Octiew, an AI-powered code review automation platform designed to eliminate PR bottlenecks and reclaim valuable developer time.
The Problem
Engineering teams lose an average of 4 days per pull request waiting for reviews. This translates to:
- 3.4 hours per developer per week wasted
- $25K+ annual cost per developer
- Frustrated teams and delayed releases
Our Solution
Octiew automates the entire code review workflow:
Smart Reviewer Assignment
Our AI analyzes your codebase and automatically assigns the most qualified reviewers based on:
- Code ownership patterns
- Domain expertise
- Current workload
- Historical review quality
Intelligent Routing
- Respects CODEOWNERS files
- Supports directory and extension patterns
- Random selection from qualified reviewers
- Automatic reassignment on decline
Seamless Integration
- GitHub integration for PR monitoring
- Slack notifications for instant alerts
- Accept/decline reviews directly from Slack
- 5-minute auto-decline timeout
How It Works: The Revolutionary Accept/Decline Process
When a PR is created, Octiew’s intelligent system springs into action:
- Analyzes the PR - Reads your CODEOWNERS file and matches changed files to owners
- Selects a reviewer - Randomly picks one codeowner (for fair load distribution)
- Direct Slack notification - The bot sends a direct message to the selected reviewer
- Accept or Decline - Reviewers can respond with one click directly in Slack
- Auto-reassignment - If declined or no response in 5 minutes, another codeowner is automatically notified
- Never goes stale - The system keeps trying (up to 2x the number of codeowners) until someone accepts
This revolutionary process ensures PRs never go stale and reviewers are never overwhelmed.
Getting Started: Step-by-Step Setup Guide
Setting up Octiew takes less than 5 minutes. Here’s exactly how to do it:
Step 1: Sign Up with GitHub
- Visit octiew.com/login
- Click “Sign in with GitHub”
- Authorize Octiew to access your GitHub profile
- You’ll be redirected to your dashboard
Step 2: Create or Join an Organization
Organizations help you manage your team and repositories.
To create a new organization:
- On your dashboard, click “Create Organization”
- Enter your organization name and description
- Click “Create” - you’re now the admin!
To join an existing organization:
- Ask your organization admin to invite you
- Accept the invitation via email or Slack
- You’ll automatically join the organization
Step 3: Subscribe to a Plan
Before connecting services, you’ll need to choose a plan:
- Click “View Pricing Plans” on your dashboard
- Choose between:
- Lifetime Pass - One-time payment, unlimited use
- Per User Monthly - Flexible monthly subscription
- Complete the Stripe checkout process
- You’ll be redirected back to your dashboard
Note: Only organization admins need to pay. Invited team members use the service for free!
Step 4: Connect Your Slack Account
This enables you to receive PR notifications directly in Slack.
- On your dashboard, click “Connect Slack”
- Choose your Slack workspace
- Authorize Octiew to send you direct messages
- You’ll see a confirmation that Slack is connected
Important: Each team member must connect their own Slack account to receive notifications.
Step 5: Install GitHub Repositories (Admin Only)
Organization admins can connect repositories to enable PR monitoring.
- Click “Connect Repositories” on your dashboard
- You’ll be redirected to GitHub’s installation page
- Select which repositories to grant Octiew access to
- Click “Install”
- You’ll be redirected back to your dashboard
Step 6: Add a CODEOWNERS File
Octiew uses your repository’s CODEOWNERS file to determine who should review each PR.
- Create a file named
CODEOWNERSin your repository root (or.github/directory) - Add ownership rules using GitHub’s CODEOWNERS syntax:
# Default owner for everything
* @engineering-team
# Frontend code
/src/frontend/ @frontend-team @alice @bob
# Backend API
/src/api/ @backend-team @charlie
# Database migrations
/migrations/ @database-admin @david
# Documentation
*.md @tech-writer @alice
# Specific file types
*.ts @typescript-experts
*.py @python-team
- Commit and push the CODEOWNERS file to your repository
Step 7: Open a Pull Request
That’s it! Now when anyone opens a PR:
- Octiew analyzes the changed files
- Matches them against your CODEOWNERS patterns
- Randomly selects one codeowner from the matched owners
- Sends a Slack DM to that person with Accept/Decline buttons
- If declined or no response in 5 minutes, automatically picks another codeowner
- Keeps trying until someone accepts (up to 2x the number of codeowners)
The selected reviewer becomes the owner of that review - they get direct notifications and can accept or decline with one click.
Why This Prevents Stale PRs
Traditional PR workflows fail because:
- ❌ Reviewers miss GitHub notifications
- ❌ No accountability - everyone assumes someone else will review
- ❌ No automatic follow-up when reviewers are busy
- ❌ PRs sit for days waiting for acknowledgment
Octiew solves this with:
- ✅ Direct Slack messages - impossible to miss
- ✅ Single reviewer assignment - clear ownership and accountability
- ✅ Accept/Decline buttons - one-click response
- ✅ 5-minute auto-reassignment - if someone’s busy, we find someone else
- ✅ Persistent retries - keeps trying until someone accepts
- ✅ Load balancing - random selection prevents reviewer burnout
Real Results
Teams using Octiew report:
- 70% faster PR turnaround time
- 90% reduction in “ping for review” Slack messages
- Zero stale PRs - every PR gets acknowledged within minutes
- $25K+ savings per developer annually
Get Started Today
Ready to eliminate PR bottlenecks and save 3.4 hours per week? Sign up now and start automating your code reviews today!
Questions? Reach out to us at octiew@dmt.dev