feat: Source Capture System + CLI scope standardization

[yansfil]

Summary

• Source Capture System - External data capture and context creation pipeline
• CLI Standardization - Consistent --global/--all scope options
• Core Principles - Added CORE_PRINCIPLE.md with 9 design guidelines
• Plugin Marketplace - Added marketplace.json for distribution
• Code Quality - Centralized DEFAULT constants to prevent fragmentation

Key Changes

Source Capture System

• ctx-capture agent for orchestrating multi-source capture
• session-capture skill for Claude Code session extraction
• /ctx.capture command as user entry point
• Inbox system (.ctx/inbox/) for temporary data storage
• Security policies in capture-policy.md

CLI Standardization

• New ctx list command with scope options
• ctx load: -k for keywords, -t for target
• ctx save: --keywords replaces --when, added --target
• All read commands: --global, --all flags
• JSON default output, --pretty for human-readable

Core Principles (CORE_PRINCIPLE.md)

1. Simplicity Over Fragmentation - One way to do things. One place to look.
2. UX Simplicity
3. CLI First
4. Scope Defaults
5. Write vs Read Distinction
6. Output Format
7. Context Distinction Criteria
8. Priority Order
9. Context Philosophy

Refactoring: Centralized DEFAULT Constants

• DEFAULT_PROJECT_CONTEXT_PATHS / DEFAULT_GLOBAL_CONTEXT_PATHS → context-path-matcher.ts (single source of truth)
• Removed duplicate definitions from init.ts, scanner.ts
• Fixed check.ts to use getProjectContextPaths() instead of hardcoded pattern
• Fixed scanner.ts global scope bug (was using project defaults for global)

Plugin Marketplace

• marketplace.json for distribution
• plugin/README.md with installation guide

Test plan

• pnpm validate passes (typecheck + build + test)
• Test ctx list with various scope options
• Test ctx load -k <keywords> and ctx load -t <target>
• Verify plugin loads correctly: claude --plugin-dir ./plugin

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @yansfil, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the CTX context management system by integrating a new Source Capture System, allowing users to easily capture and convert external data, such as Claude Code sessions, into structured context. Concurrently, it refines the command-line interface by standardizing scope options across various commands and introducing a new ctx list command, ensuring a more consistent and intuitive user experience. These changes are supported by extensive new documentation outlining core principles, security policies, and technical specifications.

Highlights

• Source Capture System: Introduces a new system for capturing external data and creating context, including a ctx-capture agent, a session-capture skill for Claude Code sessions, and a /ctx.capture command. It also establishes an inbox system (.ctx/inbox/) for temporary data storage and defines security policies for redaction and provenance tracking.
• CLI Scope Standardization: Standardizes the --global and --all options across CLI commands like ctx status, ctx load, and the newly added ctx list. Commands now default to the narrowest and safest project scope, with clear options to expand the search or operation scope.
• Documentation & Core Principles: Adds comprehensive documentation for the new source capture system, including an RFC, security policies, and inbox schema. New core principle documents (CORE_PRINCIPLE.md, docs/AGENT-PRINCIPLES.md, plugin/AGENTS.md) have been introduced to guide plugin development and agent behavior, emphasizing UX simplicity, CLI-first interaction, and safe defaults.
• Frontmatter Keyword Renaming: The when field in context frontmatter has been consistently renamed to keywords across the codebase, including in interfaces, parsing logic, CLI options, and documentation, to better reflect its purpose for keyword-based context matching.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This is an excellent and comprehensive pull request that introduces a major new feature, the Source Capture System, and significantly refactors the CLI for better consistency. The design of the new capture system is robust, with a strong emphasis on security and privacy, as evidenced by the detailed policy documents. The standardization of CLI scope options (--global, --all) and the introduction of the ctx list command greatly improve the tool's usability and predictability. The extensive updates to documentation, including new RFCs and principle guides, are commendable and will be invaluable for future development and user understanding. The code refactoring, such as centralizing the global index update, simplifies the architecture and enhances maintainability. Overall, this is a high-quality contribution that significantly advances the project.