Documentation

Learn how to use Sable Code to analyze and improve your repositories.

Quick Start

Sign in with GitHub - Connect your GitHub account to access your repositories
Select a repository - Choose from your accessible repos and pick a branch
Configure analysis - Set scope, context, and extra instructions
Review findings - See errors, warnings, security issues, and style suggestions
Create a PR - Apply fixes automatically with a pull request

AGNT-V1 Workers

Sable Code uses multiple AGNT-V1 workers to analyze your codebase in parallel. Each worker:

Analyzes a subset of files independently
Communicates findings with other workers
Never works on the same file simultaneously (file locking)
Generates patches for fixable issues

// Worker distribution

AGNT-1: /components, /hooks

AGNT-2: /lib, /utils

AGNT-3: /app, /pages

AGNT-4: /api, /server

AGNT-5: /styles, /config

Supported Languages

Full Support

TypeScript (.ts, .tsx)
JavaScript (.js, .jsx, .mjs, .cjs)
Python (.py)
HTML / CSS / SCSS

Best Effort

Lua / LuaU (.lua, .luau)
Ruby (.rb)
PHP (.php)
Shell (.sh)
SQL (.sql)

Analysis Scope

TypeScript / JavaScript

Type errors, any types, missing return types, import issues

Dead Code Detection

Unused variables, unreachable code, unused imports

Null Safety

Potential null/undefined access, missing null checks

Security Sweep

Hardcoded secrets, SQL injection, XSS vulnerabilities

Experimental Refactoring

Code smell detection, complexity reduction suggestions

Configuration

Add a .sablecode.yml file to your repository root to customize analysis:

# .sablecode.yml
version: 1

# Folders to skip during analysis
ignore:
  - node_modules
  - dist
  - build
  - .next
  - coverage
  - vendor
  - __pycache__

# Analysis scope
scope:
  typescript: true
  deadCode: true
  nullSafety: true
  security: true
  refactoring: false

# Custom instructions for AGNT-V1
instructions: |
  Focus on React best practices.
  Ignore console.log statements.

Security & Privacy

•Your code is only accessed during analysis and is not stored permanently
•GitHub tokens are encrypted at rest using AES-GCM encryption
•Analysis runs in isolated environments per report
•You can revoke access anytime from your GitHub settings