context-gathering

Gathers codebase, database, and documentation context before any code reading or editing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes made from assumptions cause rework, broken callers, and missed edge cases. This Skill enforces a mandatory pre-flight workflow that gathers full context — symbols, callers, database state, docs, and conventions — before any code exploration, editing, or code-related answer. ## Core Features & Use Cases - Mandatory Pre-Flight Checkpoint: Blocks code exploration, read/edit/write operations, and code answers until the target is clarified and context is gathered. - Six-Step Context Workflow: Clarify target, discover symbols via code navigation tools, map the codebase and database, fetch current documentation, analyze conventions, and verify readiness before acting. - Trivial-Task Fast Path: Skips the deep scan only for single-file mechanical changes with no cross-module callers, verified by a reference check. - Use Case: Before fixing a bug in a payment module, the Skill requires locating the implementation, mapping callers with find_references, checking the database schema and sample rows, and confirming conventions — only then planning the fix. ## Quick Start Invoke the context-gathering skill before reading or editing any code in this repository.

Frequently Asked Questions about context-gathering

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

FAQPage Schema
How do I gather codebase context before editing code?▼

Follow a six-step workflow: clarify the target, discover symbols with code navigation tools, map the codebase and database, fetch current documentation, analyze conventions, then verify understanding. Only plan and implement after all checks pass.

When should I use symbol navigation tools instead of grep?▼

Use code navigation tools for symbol-level work like lookups, reference tracing, and class member listing. Reserve grep, read, and file search for non-symbol tasks such as plain-text config keys, known file paths, and glob patterns.

Can I skip the context-gathering steps for small changes?▼

A fast path exists only when the file path is exactly known, the change is mechanical like a rename or one-line fix, and no cross-module callers are affected, verified with one find_references call. Convention analysis still applies.

Why verify database state before changing code?▼

Database state is ground truth for anything touching persisted data. Seeders, migrations, and factories may not reflect the current data shape, so query the schema, row counts, and sample rows directly alongside code review.

What happens if the required docs files are missing?▼

If a project-root docs spec file is missing, fall back to native tools and note the gap explicitly. Never invent the contents of missing specification files.