What your agent can ask CKB
CKB has 110 capabilities under the hood. Your agent can expand its capability set when a task needs more — reaching for the right one when a question like these comes up.
What breaks if I change this?
Blast radius, affected tests, callers and contracts — before the change happens.
Why is it built this way?
Module boundaries, architectural decisions, and the reasoning behind them.
Is this safe to ship?
Structural PR review, security scanning, dead code, CI gates, and compliance pre-checks.
For power users
All 110 capabilities
Every capability, by category — the same reference your agent draws from.
Full capabilities referenceWhat You Can Do
Ship with confidence
Capabilities that keep your repo safe, clean, and easy to change.
Compliance Audit
Map every finding to 20 regulations automatically.
GDPR, PCI DSS, HIPAA, SOC 2, ISO 27001 — one scan covers all.
$ ckb review --format=complianceFinding: Hardcoded DB credentials PCI DSS Req 2.1 HIPAA 164.312(d) SOC 2 CC6.1
Impact Analysis
See blast radius + risk before you commit.
Affected files, tests, and risk scores in one command.
$ ckb impact diffBlast radius: 12 files, 8 consumers Risk: High (UserService.go has 8 dependents) Affected tests: 5 files
Security Scanning
Find exposed secrets automatically.
26+ patterns for API keys, tokens, credentials.
$ ckb scan-secretsFound 2 potential secrets: config/aws.go:23 - AWS Access Key .env.local:8 - Database password
Ownership & Review
Get the right reviewer, instantly.
CODEOWNERS + git-blame with time decay.
$ ckb reviewersSuggested: @sarah (92% confidence) 67% of auth module commits Last active: 2 days ago
Built for Scale
Query across all your repos at once.
Incremental indexing, federation, token-optimized.
$ ckb federation search "PaymentService"Searching 3 repositories... Found in: api-svc, web-app, mobile Cross-repo dependencies: 2