Getting Started Overview

Codity Platform connects repository reviews, security checks, code intelligence and team workflows. Start with the Quickstart Guide to connect your first repository.

What Codity Does

Codity receives provider events for connected repositories, analyzes eligible changes and posts review feedback. Review configuration controls when reviews run and which checks apply. The CLI and agents provide additional ways to work with a codebase; their commands are documented separately.

What Happens After Connecting a Repository

1. Webhook Registration

GitLab, Azure DevOps and Bitbucket repository enabling configures provider notifications. GitHub uses the installed GitHub App. The provider identity must have the required access; a successful sign-in does not prove webhook setup or repository enabling succeeded.

2. Automatic Review Triggering

The enabled repository must match your trigger and branch settings. See When Reviews Run.

3. Review Comments

Check the PR/MR for review status, summaries and findings. Findings explain the issue and may suggest a fix. Timing and output vary with the change and enabled checks.

A typical finding identifies a file/line, describes a failing scenario and explains its impact. Where available, it also supplies a suggested correction. Inspect that scenario against the code and requirements before applying the suggestion. Review comments are analysis results; their presence does not mean a fix has been committed.

Regular reviews can post inline findings. Concise Mode consolidates findings into PR-level output. Enabled changed-code security, introduced-dependency and quality checks can add their own result sections. A completed review can have no findings.

4. Dashboard Updates

Use Repositories for connected repositories and review activity. Overview summarizes the active account. The account and team selections determine the context of supported views.

What You'll See First

The sidebar includes Repositories, Memory, Code Navigation, Teams, Settings and account/billing destinations where your access allows them. One-Time Runs groups individually started assessments, including repository scans, pentesting and accessibility checks; model evaluation appears when enabled for the deployment. Prices and availability are shown in the platform.

Use the product switcher for Codity One, whose discovery, connectors and operational workflows have their own documentation inside that product. Repository provider setup is covered by the provider guides, independently of Codity One GitOps connectors.

Choose Your Next Task

Task Guide
Connect and verify the first repository Quickstart
Decide when automatic reviews run Auto Review Configuration
Explain project conventions to the reviewer Custom Review Instructions
Ignore paths or add guidance for particular files Path Rules
Choose which scan pipelines run Scan Configuration
Investigate recorded delivery and review activity Analytics Access and Setup
Review code from a local terminal CLI Overview
Create an agent and configure its permissions Agents Quickstart

For the first repository, start with connection and review verification. Then change one setting at a time and inspect a subsequent review so that you can tell which change affected the result.

What Codity Does NOT Do

Code changes require the relevant action and permissions. Autofix must be enabled for its review commands. Merge enforcement also requires the appropriate provider branch rules; see Merge Gates.

A review does not guarantee that all defects or security issues have been found. Retention and processing differ between reviews, indexing, agents and assessments; do not assume that all workflows store only review metadata.