ctx

Analyze codebases using indexed symbols, dependencies, and change impact.

10|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/agentis-tools/ctx --skill ctx-agentis-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ctx
Source: https://github.com/agentis-tools/ctx/tree/main/plugins/claude/ctx/skills/ctx
Command: npx skills add https://github.com/agentis-tools/ctx --skill ctx-agentis-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid guesswork when working in unfamiliar or fast-changing codebases by using an indexed view of symbols, callers, dependencies, and change impact.

Core Features & Use Cases

  • Repository Orientation: Quickly map a codebase to understand its structure and major concepts before editing.
  • Evidence-Driven Analysis: Find existing implementations, callers, dependencies, similar code, and blast radius to support safer changes.
  • Governance and Quality Gates: Check architectural rules, score branches, inspect duplication, and assess maintenance hotspots or health trends.
  • Use Case: When reviewing a risky feature change, use this Skill to locate affected symbols, measure impact, and verify whether the branch violates repository policy.

Quick Start

Use the ctx skill to inspect the repository layout, identify the relevant symbols, and assess the change impact before making edits.

Frequently Asked Questions about ctx

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze codebase blast radius before making changes?

Analyze codebase blast radius by indexing symbols and dependency relationships to locate callers, measure change impact, and verify whether edits violate repository policy. This grounds modifications in deterministic local evidence for safer updates.

What is the best way to map an unfamiliar repository structure before editing?

Mapping an unfamiliar repository structure requires indexing symbols, callers, and dependencies to quickly orient yourself. This evidence-driven view reveals major concepts and existing implementations, reducing guesswork when navigating fast-changing codebases.

How do I detect maintenance hotspots and duplication in a codebase?

Detect maintenance hotspots and duplication by indexing the codebase and running longitudinal health analysis, duplication inspection, and branch scoring workflows. These governance checks identify risky areas and assess code quality trends over time.

Can I use dependency graph analysis for architecture governance and policy validation?

Dependency graph analysis supports architecture governance by validating policy rules, scoring branches, and inspecting structural relationships. Indexed symbols provide deterministic local evidence to enforce maintenance standards and verify compliance before merging changes.

Does codebase change impact analysis work without external dependencies?

Codebase change impact analysis works without external dependencies by using local indexing, query, and SQL snapshot workflows. These deterministic local governance tools inspect symbols and relationships internally without requiring third-party integrations.