Skip to content
Skills Library
Programming · Building & coding

config-setup

/config-setup

Set up or tune .codemap/config.json so Codemap focuses on code-relevant parts of the repo. Use when config is missing, boilerplate, noisy, or mismatched to the stack.

Repository
codemap ↗
Licence
MIT
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Set up or tune .codemap/config.json so Codemap focuses on code-relevant parts of the repo. Use when config is missing, boilerplate, noisy, or mismatched to the stack.

Original author description

Set up or tune .codemap/config.json so Codemap focuses on code-relevant parts of the repo. Use when config is missing, boilerplate, noisy, or mismatched to the stack.

How it works

  1. When this skill is matched at score 100, do this BEFORE the user's task, then continue the
  2. Goal
  3. Use this when
  4. Workflow
  5. Heuristics
  6. Example outcomes
  7. Output expectations
Original SKILL.md headings · 102 lines, 685 words
SKILL.md preview
---
name: config-setup
description: Set up or tune .codemap/config.json so Codemap focuses on code-relevant parts of the repo. Use when config is missing, boilerplate, noisy, or mismatched to the stack.
---

# Codemap Config Setup

## When this skill is matched at score 100, do this BEFORE the user's task, then continue the task

A score of 100 means a hook found the config missing, empty, malformed, or boilerplate. Fix it first; it takes under a minute and every later Codemap answer depends on it.

1. Run `codemap config show` to see the current state. If it says missing, run `codemap config init` (most commands now do this for you).
2. Write or tune `.codemap/config.json` using the workflow below: keep source extensions in `only`, add `exclude` for real noise, set `depth` if the tree is wide.
3. Rerun `codemap .` and confirm the tree is dominated by source, not assets.
4. Verify one known cross-file dependency still resolves with `codemap --importers <file>`.

Then return to the user's task. Do not skip this because the task looks small.

## Goal

Write or improve `.codemap/config.json` so future Codemap calls stay focused on the code that matters for this repo.

## Use this when

1. `.codemap/config.json` is missing
2. The existing config looks like a bare bootstrap instead of a real project policy
3. Codemap output is dominated by assets, fixtures, generated files, vendor trees, PDFs, screenshots, models, or training data
4. The project stack is obvious, but Codemap is not prioritizing the right parts of the repo

## Workflow

1. Inspect the repo quickly before writing config
   - Read the root and applicable nested `AGENTS.md` files before deciding ownership or scope
   - Read language workspace manifests such as `Cargo.toml`; preserve every declared workspace member
   - Run `codemap .`
   - If needed, run `codemap --deps .`
   - Note the stack markers (`Cargo.toml`, `Package.swift`, `*.xcodeproj`, `go.mod`, `package.json`, `pyproject.toml`, etc.)
   - Identify large non-code directories and noisy extensions

2. Decide whether config is missing, boilerplate, or tuned
   - Missing: no `.codemap/config.json`
   - Boilerplate: only generic `only` values, no real shaping, no excludes despite obvious noise
   - Tuned: contains intentional project-specific includes/excludes, depth, or routing hints

3. Write a conservative code-first config
   - Keep primary source-language `only` values when they help
   - Add `exclude` entries for obvious non-code noise
   - Set a moderate `depth` when the repo is broad
   - Avoid overfitting or excluding real source directories

4. Prefer stack-aware defaults
   - Rust: focus `src`, `tests`, `benches`, `examples`; de-prioritize corpora, sample PDFs, training data, large generated artifacts
   - For Cargo workspaces, keep all workspace members' `src`, `tests`, `benches`, and `examples` trees unless repository evidence explicitly excludes one
   - iOS/Swift: focus app/framework source, tests, package/project manifests; de-prioritize `.xcassets`, screenshots, snapshots, vendor/build outputs
   - TS/JS: focus `src`, `apps`, `packages`, `tests`; de-prioritize `dist`, `coverage`, Storybook assets, large fixture payloads
   - Python: focus package roots, tests, tool config; de-prioritize notebooks, data dumps, models, fixtures when they overwhelm code
   - Go: focus packages, cmd, internal, tests; de-prioritize generated assets, sample data, vendor-like noise

5. Preserve user intent
   - If config already looks curated, do not replace it wholesale
   - Make minimal edits and explain why

6. Verify immediately
   - Rerun `codemap .`
   - If the repo still looks noisy, refine `exclude` and possibly `depth`
   - Only rerun `codemap --deps .` after tree output looks reasonable
   - Verify at least one known cross-layer dependency remains discoverable after tuning

## Heuristics

- Exclude giant non-code directories before narrowing source extensions further
- Prefer directory exclusions over extension-only exclusions when the directory is clearly not core to the codebase
- Do not exclude tests just because they are large
- Do not exclude docs that are part of routing or subsystem understanding
- Keep the first config conservative; optimize further only if the output remains noisy

## Example outcomes

### Rust library with large fixture data

```json
{
  "only": ["rs", "toml", "md"],
  "exclude": ["training-data", "test-pdfs", "*.pdf"],
  "depth": 4
}
```

### iOS app with asset bloat

```json
{
  "only": ["swift", "m", "mm", "h", "plist", "md"],
  "exclude": [".xcassets", "Snapshots", "Screenshots", "DerivedData"],
  "depth": 4
}
```

## Output expectations

After tuning config, briefly report:

1. Why the old config was missing or too noisy
2. What exclusions or depth choices you added
3. Whether future Codemap runs should now be materially cleaner

Versions

RepositoryScoreLicence
This page · jordancoin/codemap100MIT
jordancoin/codemap100MIT

Database snapshot: 13.11.2026 · package version 1d3c3c4c6839 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100codemap-export
    Use to export the codemap as machine-readable JSON for downstream tooling. Same data as /codemap, different format. "Export the codemap", "give me the codemap as JSON".
  • 100codemap
    Analyze codebase structure, dependencies, changes, cross-agent handoffs, and get code-aware intelligence. Use when user asks about project structure, where code is located, how files connect, what changed, how to resume work, before starting any coding task, when you need risk…
  • 90rc-codemap
    Builds and refreshes per-directory codemap.md as a cheap structure map. Use before exploring a large repo. Do not use to trace one bug.
  • 100codemap
    Analyze codebase structure, dependencies, changes, cross-agent handoffs, and get code-aware intelligence. Use when user asks about project structure, where code is located, how files connect, what changed, how to resume work, before starting any coding task, when you need risk…
  • 96codemap
    Create a seven-document architecture map when the user asks to map a codebase.
  • 100codemap
    Use for evidence-based codebase documentation. Walks the repo, builds a map of components + responsibilities + interconnections. Output is hand-curated markdown with diagrams. Variants — codemap-fast, codemap-diff, codemap-trust, codemap-export.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.