gkg

Discover Pulse repository symbols and definitions via repo_map and read_definitions.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/quanpersie2001/pulse --skill gkg-quanpersie2001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gkg
Source: https://github.com/quanpersie2001/pulse/tree/main/plugins/pulse/skills/gkg
Command: npx skills add https://github.com/quanpersie2001/pulse --skill gkg-quanpersie2001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides reliable codebase intelligence for Pulse planning and discovery by turning scattered files, symbols, and definitions into concise, evidence-based artifacts that planners and reviewers can trust.

Core Features & Use Cases

  • Scout-first readiness: Start with the Pulse scout output to verify MCP availability, project indexing, and recommended actions before running discovery.
  • Primary discovery path: Use repo_map for architecture snapshots, search_codebase_definitions to locate candidate symbols, and read_definitions to gather full-definition evidence for planning artifacts.
  • Fallbacks and verification: Use get_references and get_definition only as spot helpers and fall back to local rg searches and direct file reads when MCP results are thin or unavailable; record findings in history/<feature>/discovery.md for pulse:planning.

Quick Start

Run the Pulse scout, then perform repo_map followed by search_codebase_definitions and read_definitions to produce an architecture snapshot and existing-pattern notes.

Frequently Asked Questions about gkg

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

FAQPage Schema
How do I generate an architecture snapshot for codebase planning?▼

To generate an architecture snapshot, run a Pulse scout readiness check first, then use repo_map to capture repository structure before locating specific symbols with search_codebase_definitions.

What is the best way to trace symbol definitions across a repository?▼

Tracing symbol definitions involves using search_codebase_definitions to locate candidate symbols, followed by read_definitions to gather full-definition evidence for your planning artifacts.

Can I search codebase definitions if the MCP server is unavailable?▼

Yes, you can search codebase definitions when MCP is unavailable by falling back to local ripgrep searches and direct file reads to verify symbols and collect evidence.

Do I need a scout readiness check before exploring a repo map?▼

Yes, a scout readiness check is required before exploring a repo map to verify MCP availability, confirm project indexing, and validate recommended actions for discovery.

How do I collect evidence for planning artifacts from a codebase?▼

Collect evidence for planning artifacts by using read_definitions after locating symbols via search_codebase_definitions, then record findings in history/<feature>/discovery.md for pulse:planning.

Why use repo_map before searching for specific code definitions?▼

Using repo_map before searching for code definitions provides an architecture snapshot that contextualizes where symbols live, ensuring targeted and accurate discovery.