building-code-context

Curate minimal multi-file repository context packs for downstream coding tasks.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/Sailfishc/guanfu --skill building-code-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: building-code-context
Source: https://github.com/Sailfishc/guanfu/tree/main/skills/building-code-context
Command: npx skills add https://github.com/Sailfishc/guanfu --skill building-code-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds the smallest sufficient context pack for a downstream coding task, when files, tests, or configs are unknown or evolving.

Core Features & Use Cases

  • Curates relevant files, tests, configs, and contracts around a target module to enable planning, debugging, reviewing, refactoring, or handoff.
  • Supports multi-file contexts across modules, branches, or environments, ensuring deterministic context packs for agents.
  • Use case: When starting a refactor with limited starting points, generate a compact context pack that guides collaboration and verification.

Quick Start

Identify the target module and generate a minimal, handoff-ready context pack that includes the most relevant surrounding files, tests, and configs.

Frequently Asked Questions about building-code-context

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

FAQPage Schema
How do I gather multi-file repository context for agent planning and debugging?

To gather multi-file repository context, curate the smallest sufficient set of target files, tests, and configs to produce a deterministic context pack for downstream agent planning and debugging.

What is the best way to prepare a code context pack for a complex refactor?

The best way to prepare a code context pack for a complex refactor is to identify target modules and extract surrounding tests and contracts, ensuring a minimal, handoff-ready context for verification.

How do I build deterministic context packs across modules and branches?

Build deterministic context packs across modules and branches by identifying target files and surrounding configs, generating a compact, handoff-ready context pack for agents to consume.

Can I use a context pack for handoff when files and contracts are still evolving?

Yes, you can use a context pack for handoff when files and contracts are evolving; it identifies the relevant target files and surrounding tests to ensure a sufficient context for collaboration.

What files should I include in a multi-file context pack for an unknown codebase?

Include target files, surrounding tests, configs, and contracts in a multi-file context pack to ensure the smallest sufficient context is established for downstream planning and reviewing.

Why does my agent fail to plan refactors with limited starting points in a repository?

Agents fail to plan refactors with limited starting points because they lack sufficient context; generating a minimal context pack of relevant files and tests provides the necessary surrounding code for guidance.