repo-context-gathering

Name: repo-context-gathering
Availability: InStock
Author: hoshiyar-singh8

Detect repo archetypes and gather architecture, DI, GraphQL, and testing context.

Updated Mar 16, 2026

Search Tags:#automation #architecture #context #graphql #viper #repo-analysis #archetype-detection

Ready to run

npx skills add https://github.com/hoshiyar-singh8/SprintPlanner --skill repo-context-gathering

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-context-gathering
Source: https://github.com/hoshiyar-singh8/SprintPlanner/tree/main/skills/repo-context-gathering
Command: npx skills add https://github.com/hoshiyar-singh8/SprintPlanner --skill repo-context-gathering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects repo archetypes and gathers only the essential architecture, DI, GraphQL, and testing context needed to edit or extend a feature safely and efficiently.

Core Features & Use Cases

Archetype detection: identifies whether the repo is a B2C/Bento module or classic VIPER, GraphQL feed, or modular SDK pattern.
Context deduction: collects a minimal set of files that prove the local architecture and data flow, reducing cognitive load when starting a change.
Context reuse: outputs a ready-to-use context pack for downstream edits, testing, or scaffolding.
Use Case: When starting work on a Bento feature, run this skill to obtain the exact repository pattern and relevant files (builder, DI, mapper, etc.) to guide your implementation.

Quick Start

Provide a compact repo context pack with proven archetypes for the target feature.

Frequently Asked Questions about repo-context-gathering

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

FAQPage Schema

How do I gather minimal architecture context before editing a feature in a large codebase?▼

To gather architecture context, scan the repository to detect structural archetypes like VIPER, GraphQL feed, modular SDK, or Bento patterns. This identifies the relevant files and data flow, producing a concise context pack that reduces cognitive load before making codebase edits.

What is repo archetype detection and how does it help with codebase analysis?▼

Repo archetype detection identifies whether a repository follows classic VIPER, GraphQL feed, modular SDK, or B2C/Bento module patterns. It helps codebase analysis by collecting only the essential files proving local architecture, ensuring you edit or extend features safely without scanning the entire codebase.

Can I automatically detect VIPER and GraphQL feed patterns when starting a new feature?▼

Yes, you can automatically detect VIPER and GraphQL feed patterns by scanning the repository structure. The analysis deduces the local architecture and data flow, outputting a ready-to-use context pack with relevant files and recommended next steps to guide your feature implementation.

What's the best way to find relevant builder and dependency injection files for a Bento module?▼

The best way to find relevant builder and dependency injection files is to run a context deduction scan for the Bento module archetype. This collects the minimal set of files proving the local architecture and data flow, providing a focused context pack for downstream edits.

Does repo context gathering work for modular SDK patterns and output testing guidance?▼

Yes, repo context gathering works for modular SDK patterns by detecting the archetype and deducing the minimal architecture context. It outputs relevant files along with guidance for downstream edits and testing, ensuring you can safely extend the SDK feature.