repomix-context

Generates bounded Repomix repository context packs with strict scope and security controls.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/369sup/support --skill repomix-context-369sup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repomix-context
Source: https://github.com/369sup/support/tree/main/plugins/repomix-context/skills/repomix-context
Command: npx skills add https://github.com/369sup/support --skill repomix-context-369sup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Large repository tasks often need broad context that semantic navigation cannot efficiently provide, but indiscriminate packing risks leaking secrets and producing bloated, unverifiable output. This Skill governs when and how to use Repomix so generated context stays minimal, safe, and disposable. ## Core Features & Use Cases - Decision Gate: Forces narrower discovery (declarations, references, targeted search) before any Repomix pack, so packing only happens when genuinely necessary. - Scope and Security Policy: Defines include ordering, a mandatory exclusion floor for secrets, dependencies, and generated output, plus verification of findings against original source files. - Generated Reference Governance: Controls --skill-generate snapshots as non-authoritative caches with recorded source commits, versions, and cleanup rules. - Use Case: During a cross-module architecture analysis, define the smallest include patterns, pack to a temporary location, verify material findings in original files, and delete the artifact when done. ## Quick Start Use the repomix-context skill to prepare the smallest safe Repomix context for analyzing how the modules in this repository interact.

Frequently Asked Questions about repomix-context

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

FAQPage Schema
When should I use Repomix for repository analysis?▼

Use Repomix only when semantic navigation, targeted file search, and adjacent tests cannot answer the question efficiently. It suits cross-module discovery, repository-wide architecture analysis, and long tasks needing broad context.

How do I pack a repository with Repomix safely?▼

Define the smallest include patterns, review .gitignore and .repomixignore, and explicitly exclude secrets, credentials, dependencies, and generated output. Write output outside the working tree and never rely on automatic security scanning alone.

When should I not use Repomix?▼

Avoid Repomix for known files, isolated symbols, targeted edits, or facts already available from authoritative source files. Narrower tools like declaration lookup and reference search answer those questions faster and more accurately.

Can Repomix output be treated as authoritative documentation?▼

No. Packed output and generated reference Skills are disposable discovery caches, not authoritative sources. Every material finding must be reopened and verified in the original source files before decisions or edits.

What should a Repomix-generated reference Skill record?▼

Record the repository, exact commit, dirty-state caveat, generation time, Repomix version, include and exclude patterns, and compression choice. Mark it non-authoritative and keep it out of version control unless explicitly requested.