gsd-intel

Query, check freshness, and rebuild codebase intelligence indexes in .planning/intel/.

264|11|Updated Apr 25, 2026

Search Tags:#indexing #codebase #analysis #diff #status #refresh #intel

Ready to run

npx skills add https://github.com/coco-research/coco --skill gsd-intel-coco-research

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-intel
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-intel
Command: npx skills add https://github.com/coco-research/coco --skill gsd-intel-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you inspect, search, and refresh the codebase intelligence files that power repository-aware analysis, so you can quickly understand what the project knows about its own structure.

Core Features & Use Cases

Query intelligence: Search indexed intel entries for a term and retrieve matching notes from .planning/intel/.
Check freshness: Review status and diff information to see whether the intelligence index is current or stale.
Rebuild indexes: Refresh the intel files when the repository has changed and you need updated architecture, dependency, or file-role summaries.

Quick Start

Use the gsd-intel skill to check the current intel status for this repository.

Frequently Asked Questions about gsd-intel

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

FAQPage Schema

How do I check if my codebase intelligence index is stale or outdated?▼

You can check codebase intelligence freshness by reviewing the status and diff information stored in .planning/intel/ to determine whether the index reflects current repository changes or requires a refresh.

What is the best way to search indexed analysis terms in a repository?▼

Searching indexed analysis terms involves querying the codebase intelligence entries in .planning/intel/ to retrieve matching notes and architecture summaries without scanning the entire codebase manually.

How do I rebuild codebase intelligence indexes after updating my repository?▼

To rebuild codebase intelligence indexes, trigger a refresh operation that regenerates architecture, dependency, and file-role summary files by parsing project data and spawning controlled tasks for deterministic updates.

Does this codebase indexing approach work without external dependencies?▼

Yes, this codebase indexing approach operates with no external dependencies, requiring only direct access to project files, JSON parsing capabilities, and timestamp tracking to manage intelligence files.

Why does my codebase intelligence snapshot show a diff when no files changed?▼

Codebase intelligence snapshot diffs can appear due to timestamp tracking inconsistencies or controlled task spawning variations during deterministic intel updates, requiring an index rebuild to synchronize the stored state.

When do I need to refresh codebase architecture and dependency data?▼

You need to refresh codebase architecture and dependency data when the repository structure changes significantly, ensuring the intelligence index in .planning/intel/ accurately reflects current file roles and dependency relationships.