Agent skill

Gsd Codebase Mapper

by allgpt-co in allgpt-co/QuickVoice

Explores codebase and writes structured analysis documents. An agent skill from allgpt-co/QuickVoice.

MITAuto-check: notesDevelopment

Install Gsd Codebase Mapper

skills CLI
$ npx skills add allgpt-co/QuickVoice --skill gsd-codebase-mapper -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install allgpt-co/QuickVoice gsd-codebase-mapper --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/allgpt-co/QuickVoice.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/gsd/agents/codebase-mapper .claude/skills/gsd-codebase-mapper && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gsd-codebase-mapper
GitHub stars
488
Used in
1 other repo
Token cost
~3.5k tokens
SKILL.md length
629 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Explores codebase and writes structured analysis documents. An agent skill from allgpt-co/QuickVoice.

  • Works in 5 steps: Parse Focus Area → Determine Output Documents → Explore Codebase → …
  • Development work in your project
  • SKILL.md covers When to Use, Focus Areas, Core Responsibilities and Why This Matters, plus 12 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Gsd Codebase Mapper is an agent skill from allgpt-co/QuickVoice. Explores codebase and writes structured analysis documents. Spawned by map-codebase with a focus area.

Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: Open-source, self-hostable platform for building and operating AI phone agents. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “Use the gsd-codebase-mapper skill to explore codebase and writes structured analysis documents. An agent skill from allgpt-co/QuickVoice”
  • “/gsd-codebase-mapper”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Parse Focus Area
  2. Determine Output Documents
  3. Explore Codebase
  4. Write Documents
  5. Return Confirmation

What it can do on your machine

Read from SKILL.md and the folder at commit 89fa8ff. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown, bash and typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gsd Codebase Mapper loads about 3.5k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 629 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:89
    ls -la *.config.* .env* tsconfig.json .nvmrc .python-version 2>/dev/null

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from allgpt-co/QuickVoice at commit 89fa8ff, republished under its MIT licence (© allgpt-co). 629 words, ~3,512 tokens.

Download SKILL.mdSave it as .claude/skills/gsd-codebase-mapper/SKILL.md (or your agent's skills folder).
name
gsd-codebase-mapper
description
Explores codebase and writes structured analysis documents. Spawned by map-codebase with a focus area.
version
1.0.0
author
GSD Project
tags
codebase, analysis, documentation
triggers
map codebase, analyze codebase, explore codebase
tools
Read, Bash, Grep, Glob, Write

GSD Codebase Mapper

Explores a codebase for a specific focus area and writes analysis documents directly to .planning/codebase/.

When to Use

Use this agent when:

  • You need to understand an existing codebase structure
  • Starting work on a brownfield project (existing code)
  • Need to document technology stack, architecture, or patterns
  • Want to identify technical debt and concerns
  • Preparing for a new phase that requires codebase context

Focus Areas

The mapper is spawned with one of four focus areas:

  • tech - Analyze technology stack and external integrations → writes STACK.md and INTEGRATIONS.md
  • arch - Analyze architecture and file structure → writes ARCHITECTURE.md and STRUCTURE.md
  • quality - Analyze coding conventions and testing patterns → writes CONVENTIONS.md and TESTING.md
  • concerns - Identify technical debt and issues → writes CONCERNS.md

Core Responsibilities

  1. Explore thoroughly - Read relevant files, understand patterns, identify key components
  2. Write directly - Create documents in .planning/codebase/ to reduce orchestrator context load
  3. Be prescriptive - Document HOW things are done, not just WHAT exists
  4. Include file paths - Every finding should have a file path in backticks for navigation
  5. Return confirmation only - Don't return document contents, just confirm what was written

Why This Matters

These documents are consumed by other GSD commands:

/gsd:plan-phase loads relevant codebase docs when creating implementation plans:

Phase TypeDocuments Loaded
UI, frontend, componentsCONVENTIONS.md, STRUCTURE.md
API, backend, endpointsARCHITECTURE.md, CONVENTIONS.md
database, schema, modelsARCHITECTURE.md, STACK.md
testing, testsTESTING.md, CONVENTIONS.md
integration, external APIINTEGRATIONS.md, STACK.md
refactor, cleanupCONCERNS.md, ARCHITECTURE.md
setup, configSTACK.md, STRUCTURE.md

/gsd:execute-phase references codebase docs to:

  • Follow existing conventions when writing code
  • Know where to place new files (STRUCTURE.md)
  • Match testing patterns (TESTING.md)
  • Avoid introducing more technical debt (CONCERNS.md)

Process

Step 1: Parse Focus Area

Read the focus area from your prompt. It will be one of: tech, arch, quality, concerns.

Step 2: Determine Output Documents

Based on focus, determine which documents to write:

  • tech → STACK.md, INTEGRATIONS.md
  • arch → ARCHITECTURE.md, STRUCTURE.md
  • quality → CONVENTIONS.md, TESTING.md
  • concerns → CONCERNS.md
Step 3: Explore Codebase

Use appropriate exploration commands for your focus area:

For tech focus:

bash
# Package manifests
ls package.json requirements.txt Cargo.toml go.mod pyproject.toml 2>/dev/null
cat package.json 2>/dev/null | head -100

# Config files
ls -la *.config.* .env* tsconfig.json .nvmrc .python-version 2>/dev/null

# Find SDK/API imports
grep -r "import.*stripe\|import.*supabase\|import.*aws\|import.*@" src/ --include="*.ts" --include="*.tsx" 2>/dev/null | head -50

For arch focus:

bash
# Directory structure
find . -type d -not -path '*/node_modules/*' -not -path '*/.git/*' | head -50

# Entry points
ls src/index.* src/main.* src/app.* src/server.* app/page.* 2>/dev/null

# Import patterns to understand layers
grep -r "^import" src/ --include="*.ts" --include="*.tsx" 2>/dev/null | head -100

For quality focus:

bash
# Linting/formatting config
ls .eslintrc* .prettierrc* eslint.config.* biome.json 2>/dev/null
cat .prettierrc 2>/dev/null

# Test files and config
ls jest.config.* vitest.config.* 2>/dev/null
find . -name "*.test.*" -o -name "*.spec.*" | head -30

# Sample source files for convention analysis
ls src/**/*.ts 2>/dev/null | head -10

For concerns focus:

bash
# TODO/FIXME comments
grep -rn "TODO\|FIXME\|HACK\|XXX" src/ --include="*.ts" --include="*.tsx" 2>/dev/null | head -50

# Large files (potential complexity)
find src/ -name "*.ts" -o -name "*.tsx" | xargs wc -l 2>/dev/null | sort -rn | head -20

# Empty returns/stubs
grep -rn "return null\|return \[\]\|return {}" src/ --include="*.ts" --include="*.tsx" 2>/dev/null | head -30
Step 4: Write Documents

Write documents to .planning/codebase/ using the templates. Use the Write tool.

Document naming: UPPERCASE.md (e.g., STACK.md, ARCHITECTURE.md)

Template filling:

  1. Replace [YYYY-MM-DD] with current date
  2. Replace [Placeholder text] with findings from exploration
  3. If something is not found, use "Not detected" or "Not applicable"
  4. Always include file paths with backticks
Show full SKILL.md (237 more words)Show less
Step 5: Return Confirmation

Return a brief confirmation. DO NOT include document contents.

Format:

## Mapping Complete

**Focus:** {focus}
**Documents written:**
- `.planning/codebase/{DOC1}.md` ({N} lines)
- `.planning/codebase/{DOC2}.md` ({N} lines)

Ready for orchestrator summary.

Document Templates

STACK.md Template
markdown
# Technology Stack

**Analysis Date:** [YYYY-MM-DD]

## Languages

**Primary:**
- [Language] [Version] - [Where used]

**Secondary:**
- [Language] [Version] - [Where used]

## Runtime

**Environment:**
- [Runtime] [Version]

**Package Manager:**
- [Manager] [Version]
- Lockfile: [present/missing]

## Frameworks

**Core:**
- [Framework] [Version] - [Purpose]

**Testing:**
- [Framework] [Version] - [Purpose]

**Build/Dev:**
- [Tool] [Version] - [Purpose]

## Key Dependencies

**Critical:**
- [Package] [Version] - [Why it matters]

**Infrastructure:**
- [Package] [Version] - [Purpose]

## Configuration

**Environment:**
- [How configured]
- [Key configs required]

**Build:**
- [Build config files]

## Platform Requirements

**Development:**
- [Requirements]

**Production:**
- [Deployment target]

---

*Stack analysis: [date]*
ARCHITECTURE.md Template
markdown
# Architecture

**Analysis Date:** [YYYY-MM-DD]

## Pattern Overview

**Overall:** [Pattern name]

**Key Characteristics:**
- [Characteristic 1]
- [Characteristic 2]
- [Characteristic 3]

## Layers

**[Layer Name]:**
- Purpose: [What this layer does]
- Location: `[path]`
- Contains: [Types of code]
- Depends on: [What it uses]
- Used by: [What uses it]

## Data Flow

**[Flow Name]:**

1. [Step 1]
2. [Step 2]
3. [Step 3]

**State Management:**
- [How state is handled]

## Key Abstractions

**[Abstraction Name]:**
- Purpose: [What it represents]
- Examples: `[file paths]`
- Pattern: [Pattern used]

## Entry Points

**[Entry Point]:**
- Location: `[path]`
- Triggers: [What invokes it]
- Responsibilities: [What it does]

## Error Handling

**Strategy:** [Approach]

**Patterns:**
- [Pattern 1]
- [Pattern 2]

## Cross-Cutting Concerns

**Logging:** [Approach]
**Validation:** [Approach]
**Authentication:** [Approach]

---

*Architecture analysis: [date]*
STRUCTURE.md Template
markdown
# Codebase Structure

**Analysis Date:** [YYYY-MM-DD]

## Directory Layout

[project-root]/ ├── [dir]/ # [Purpose] ├── [dir]/ # [Purpose] └── [file] # [Purpose]


## Directory Purposes

**[Directory Name]:**
- Purpose: [What lives here]
- Contains: [Types of files]
- Key files: `[important files]`

## Key File Locations

**Entry Points:**
- `[path]`: [Purpose]

**Configuration:**
- `[path]`: [Purpose]

**Core Logic:**
- `[path]`: [Purpose]

**Testing:**
- `[path]`: [Purpose]

## Naming Conventions

**Files:**
- [Pattern]: [Example]

**Directories:**
- [Pattern]: [Example]

## Where to Add New Code

**New Feature:**
- Primary code: `[path]`
- Tests: `[path]`

**New Component/Module:**
- Implementation: `[path]`

**Utilities:**
- Shared helpers: `[path]`

## Special Directories

**[Directory]:**
- Purpose: [What it contains]
- Generated: [Yes/No]
- Committed: [Yes/No]

---

*Structure analysis: [date]*
CONVENTIONS.md Template
markdown
# Coding Conventions

**Analysis Date:** [YYYY-MM-DD]

## Naming Patterns

**Files:**
- [Pattern observed]

**Functions:**
- [Pattern observed]

**Variables:**
- [Pattern observed]

**Types:**
- [Pattern observed]

## Code Style

**Formatting:**
- [Tool used]
- [Key settings]

**Linting:**
- [Tool used]
- [Key rules]

## Import Organization

**Order:**
1. [First group]
2. [Second group]
3. [Third group]

**Path Aliases:**
- [Aliases used]

## Error Handling

**Patterns:**
- [How errors are handled]

## Logging

**Framework:** [Tool or "console"]

**Patterns:**
- [When/how to log]

## Comments

**When to Comment:**
- [Guidelines observed]

**JSDoc/TSDoc:**
- [Usage pattern]

## Function Design

**Size:** [Guidelines]

**Parameters:** [Pattern]

**Return Values:** [Pattern]

## Module Design

**Exports:** [Pattern]

**Barrel Files:** [Usage]

---

*Convention analysis: [date]*
TESTING.md Template
markdown
# Testing Patterns

**Analysis Date:** [YYYY-MM-DD]

## Test Framework

**Runner:**
- [Framework] [Version]
- Config: `[config file]`

**Assertion Library:**
- [Library]

**Run Commands:**
```bash
[command]              # Run all tests
[command]              # Watch mode
[command]              # Coverage

Test File Organization

Location:

  • [Pattern: co-located or separate]

Naming:

  • [Pattern]

Structure:

[Directory pattern]

Test Structure

Suite Organization:

typescript
[Show actual pattern from codebase]

Patterns:

  • [Setup pattern]
  • [Teardown pattern]
  • [Assertion pattern]

Mocking

Framework: [Tool]

Patterns:

typescript
[Show actual mocking pattern from codebase]

What to Mock:

  • [Guidelines]

What NOT to Mock:

  • [Guidelines]

Fixtures and Factories

Test Data:

typescript
[Show pattern from codebase]

Location:

  • [Where fixtures live]

Coverage

Requirements: [Target or "None enforced"]

View Coverage:

bash
[command]

Test Types

Unit Tests:

  • [Scope and approach]

Integration Tests:

  • [Scope and approach]

E2E Tests:

  • [Framework or "Not used"]

Common Patterns

Async Testing:

typescript
[Pattern]

Error Testing:

typescript
[Pattern]

Testing analysis: [date]


### INTEGRATIONS.md Template

```markdown
# External Integrations

**Analysis Date:** [YYYY-MM-DD]

## APIs & External Services

**[Category]:**
- [Service] - [What it's used for]
  - SDK/Client: [package]
  - Auth: [env var name]

## Data Storage

**Databases:**
- [Type/Provider]
  - Connection: [env var]
  - Client: [ORM/client]

**File Storage:**
- [Service or "Local filesystem only"]

**Caching:**
- [Service or "None"]

## Authentication & Identity

**Auth Provider:**
- [Service or "Custom"]
  - Implementation: [approach]

## Monitoring & Observability

**Error Tracking:**
- [Service or "None"]

**Logs:**
- [Approach]

## CI/CD & Deployment

**Hosting:**
- [Platform]

**CI Pipeline:**
- [Service or "None"]

## Environment Configuration

**Required env vars:**
- [List critical vars]

**Secrets location:**
- [Where secrets are stored]

## Webhooks & Callbacks

**Incoming:**
- [Endpoints or "None"]

**Outgoing:**
- [Endpoints or "None"]

---

*Integration audit: [date]*
CONCERNS.md Template
markdown
# Codebase Concerns

**Analysis Date:** [YYYY-MM-DD]

## Tech Debt

**[Area/Component]:**
- Issue: [What's the shortcut/workaround]
- Files: `[file paths]`
- Impact: [What breaks or degrades]
- Fix approach: [How to address it]

## Known Bugs

**[Bug description]:**
- Symptoms: [What happens]
- Files: `[file paths]`
- Trigger: [How to reproduce]
- Workaround: [If any]

## Security Considerations

**[Area]:**
- Risk: [What could go wrong]
- Files: `[file paths]`
- Current mitigation: [What's in place]
- Recommendations: [What should be added]

## Performance Bottlenecks

**[Slow operation]:**
- Problem: [What's slow]
- Files: `[file paths]`
- Cause: [Why it's slow]
- Improvement path: [How to speed up]

## Fragile Areas

**[Component/Module]:**
- Files: `[file paths]`
- Why fragile: [What makes it break easily]
- Safe modification: [How to change safely]
- Test coverage: [Gaps]

## Scaling Limits

**[Resource/System]:**
- Current capacity: [Numbers]
- Limit: [Where it breaks]
- Scaling path: [How to increase]

## Dependencies at Risk

**[Package]:**
- Risk: [What's wrong]
- Impact: [What breaks]
- Migration plan: [Alternative]

## Missing Critical Features

**[Feature gap]:**
- Problem: [What's missing]
- Blocks: [What can't be done]

## Test Coverage Gaps

**[Untested area]:**
- What's not tested: [Specific functionality]
- Files: `[file paths]`
- Risk: [What could break unnoticed]
- Priority: [High/Medium/Low]

---

*Concerns audit: [date]*

Critical Rules

  • WRITE DOCUMENTS DIRECTLY - Do not return findings to orchestrator. The whole point is reducing context transfer.
  • ALWAYS INCLUDE FILE PATHS - Every finding needs a file path in backticks. No exceptions.
  • USE THE TEMPLATES - Fill in the template structure. Don't invent your own format.
  • BE THOROUGH - Explore deeply. Read actual files. Don't guess.
  • RETURN ONLY CONFIRMATION - Your response should be ~10 lines max. Just confirm what was written.
  • DO NOT COMMIT - The orchestrator handles git operations.

Success Criteria

  • Focus area parsed correctly
  • Codebase explored thoroughly for focus area
  • All documents for focus area written to .planning/codebase/
  • Documents follow template structure
  • File paths included throughout documents
  • Confirmation returned (not document contents)
  • @skills/gsd/commands/map-codebase - Command that spawns this agent
  • @skills/gsd/references/git-integration - Git workflow patterns

© allgpt-co, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/gsd/agents/codebase-mapper of allgpt-co/QuickVoice.

Open the folder on GitHubat commit 89fa8ff

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in allgpt-co/QuickVoice, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Gsd Codebase Mapper next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gsd Codebase Mapper compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gsd Codebase Mapper this skillallgpt-co/QuickVoice4881 repos~3.5kAutomated safety check: NotesMIT
Backend Code Reviewlanggenius/dify158k—~676Automated safety check: PassCustom licence
Native Data FetchingCherryHQ/cherry-studio-app4k6 repos~2.9kAutomated safety check: NotesMIT
Twenty App Entity Developmenttwentyhq/twenty58k—~1.8kAutomated safety check: PassCustom licence
Go Pedantrychromedp/chromedp13k—~3.7kAutomated safety check: PassMIT
Gumroad Prod Consoleantiwork/gumroad9.8k—~2.9kAutomated safety check: NotesMIT

Similar skills

  • Backend Code Review

    langgenius/dify

    Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.

    158k GitHub stars~676 tokensUpdated today
    DevelopmentAuto-check passed
  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes
  • Guides changes to an existing Twenty app: adding or editing objects, layouts, logic functions and front components, with a plan stated before multi-entity edits.

    58k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Go Pedantry

    chromedp/chromedp

    This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…

    13k GitHub stars~3.7k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Gumroad Prod Console

    antiwork/gumroad

    Execute read-only Ruby/Rails commands against Gumroad's production database for debugging and investigation.

    9.8k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check: notes
  • LangBot Plugin Development

    langbot-app/LangBot

    Guides building, debugging and testing LangBot plugins: components, SDK calls, README and locale rules, SDK pitfalls and WebSocket-based testing.

    18k GitHub stars~3.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from allgpt-co/QuickVoice

All 12 skills in this repo
  • Livekit Agents

    allgpt-co/QuickVoice

    Build voice AI agents with LiveKit Cloud and the Agents SDK.

    488 GitHub stars~3.3k tokensUpdated 3 days ago
    Auto-check: notes
  • Gsd Phase Researcher

    allgpt-co/QuickVoice

    Researches phase implementation for planning. An agent skill from allgpt-co/QuickVoice.

    488 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Gsd Project Researcher

    allgpt-co/QuickVoice

    Researches domain ecosystem for project initialization. An agent skill from allgpt-co/QuickVoice.

    488 GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check passed
  • Gsd Research Synthesizer

    allgpt-co/QuickVoice

    Synthesizes research outputs from parallel researcher agents into SUMMARY.md.

    488 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Gsd

    allgpt-co/QuickVoice

    Get Shit Done (GSD) - A comprehensive project management system for solo developers using Claude agents

    488 GitHub stars~2k tokensUpdated 3 days ago
    Auto-check passed
  • Gsd Integration Checker

    allgpt-co/QuickVoice

    Verifies that integrations work correctly by checking endpoints, responses, and data flow.

    488 GitHub stars~2.8k tokensUpdated 3 days ago
    Auto-check passed

Questions about Gsd Codebase Mapper

What does Gsd Codebase Mapper do?

Explores codebase and writes structured analysis documents. An agent skill from allgpt-co/QuickVoice. Gsd Codebase Mapper is an agent skill from allgpt-co/QuickVoice. Explores codebase and writes structured analysis documents.

When should I use Gsd Codebase Mapper?

Gsd Codebase Mapper fits situations like: development work in your project.

How do I install Gsd Codebase Mapper in Claude Code?

Run `npx skills add allgpt-co/QuickVoice --skill gsd-codebase-mapper -a claude-code`. Or copy the skill folder (.claude/skills/gsd/agents/codebase-mapper in allgpt-co/QuickVoice) into .claude/skills/gsd-codebase-mapper in your project. Claude Code loads it when a task matches its description.

How do I install Gsd Codebase Mapper in Codex?

Run `npx skills add allgpt-co/QuickVoice --skill gsd-codebase-mapper -a codex`. Or copy the skill folder (.claude/skills/gsd/agents/codebase-mapper in allgpt-co/QuickVoice) into .agents/skills/gsd-codebase-mapper in your project. Codex loads it when a task matches its description.

Can I use Gsd Codebase Mapper in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add allgpt-co/QuickVoice --skill gsd-codebase-mapper -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gsd-codebase-mapper, .gemini/skills/gsd-codebase-mapper, .github/skills/gsd-codebase-mapper and .opencode/skills/gsd-codebase-mapper in your project.

What does Gsd Codebase Mapper need to run?

SKILL.md names no scripts, command-line tools or credentials: Gsd Codebase Mapper is instructions for the agent only.

Does Gsd Codebase Mapper access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gsd Codebase Mapper safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Gsd Codebase Mapper use?

Gsd Codebase Mapper is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gsd Codebase Mapper use?

About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gsd Codebase Mapper?

Skills that share tags, products or a category with Gsd Codebase Mapper: Backend Code Review (langgenius/dify, 158k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Twenty App Entity Development (twentyhq/twenty, 58k stars) and Go Pedantry (chromedp/chromedp, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gsd Codebase Mapper?

allgpt-co (a GitHub organization) maintains it in allgpt-co/QuickVoice, which has 488 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 5, 2026.

Source: allgpt-co/QuickVoice on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.