# Git Repositories That Understand Code

> Semantic repository management with AI-powered code analysis, intelligent merge strategies, and autonomous workflow automation. Analyze codebases in seconds, track technical debt, and coordinate multi-repo changes across 300+ edge locations.

Canonical: https://repo.do/

## In code

```ts
import { Repo } from 'repo.do'

// AI-powered code review and analysis
const repo = Repo({ url: 'github.com/org/repo', analyze: true })

on.PullRequest.opened($ => {
  const review = repo.analyze.Changes({ diff: $.diff })
  $.GitHub.create.Review({ pr: $.number, body: review.summary })
})

// Track technical debt automatically
repo.every.week($ => repo.create.Issues($.analyze.TechnicalDebt()))
```

## Frequently asked questions

### What makes repo.do different from GitHub or GitLab?

Repo.do adds AI-native capabilities on top of your existing Git hosting. We integrate with GitHub, GitLab, Bitbucket, and self-hosted Git to provide semantic code analysis, autonomous code review, technical debt tracking, and multi-repo coordination. Your repos stay where they are—we add intelligence without migration. Think of it as an AI layer for your version control.

### How does AI code review work?

AI analyzes pull requests for bugs, security issues, performance problems, and style violations. Reviews understand semantic meaning of code changes, not just syntax. Suggests specific fixes with code snippets. Reviews adapt to your codebase patterns and team conventions. Human reviewers focus on architecture and business logic while AI catches common issues. Average review time: <30 seconds for typical PRs.

### Can I track dependencies across multiple repositories?

Yes. Repo.do builds a dependency graph across all your repositories, tracking both direct and transitive dependencies. Detect breaking changes before they propagate. Identify which repos need updates when shared libraries change. Coordinate version bumps across microservices automatically. Support for monorepos, polyrepos, and hybrid architectures. Visualize dependencies with interactive graphs.

### How do you handle merge conflicts automatically?

AI attempts automatic conflict resolution using semantic understanding of code intent. For simple conflicts (imports, formatting), auto-merge safely. For complex conflicts, AI suggests resolution strategies with preview diffs. Human approval required for high-risk merges. Track conflict patterns to prevent future issues. Support for custom merge strategies per file type or directory. Rollback capabilities if auto-merge causes issues.

### What about security and compliance scanning?

Continuous security scanning for vulnerabilities, exposed secrets, and compliance violations. Integration with CVE databases, OWASP standards, and industry-specific compliance frameworks (SOC2, HIPAA, PCI-DSS). Automatic dependency updates for security patches. Secret detection prevents credential commits. License compliance tracking for open source dependencies. Audit logs of all code changes and access patterns.

## Part of Platform.do

repo.do is one of the primitives of Platform.do. Every .do shares one grammar, Business-as-Code, and one SDK.

- What is Business-as-Code? https://platform.do/business-as-code
- Platform.do: https://platform.do/
- Docs: https://docs.platform.do