Skip to content
Back to skills

Brownfield Gaps

ASecurity

Improves graph coverage for a specific file with dynamic/unannotated patterns (event emitters, dynamic require, global injection). Use when dep-graph shows gaps on a file or when chat/query returns "not mapped". Not for querying — only for improving coverage.

  • 4 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 12, 2026
toolsbashnode

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 12, 2026

npx -y skills add aibot88/sec_skill_store --skill brownfield-gaps --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Brownfield Gaps?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Brownfield Gaps
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aibot88-brownfield-gaps/badge)](https://www.skillsdirectory.com/skills/aibot88-brownfield-gaps)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: brownfield-gaps
description: Improves graph coverage for a specific file with dynamic/unannotated patterns (event emitters, dynamic require, global injection). Use when dep-graph shows gaps on a file or when chat/query returns "not mapped". Not for querying — only for improving coverage.
permissions:
  allow:
    - Bash(wednesday-skills fill-gaps *)
    - Bash(wednesday-skills analyze *)
---

> **Deprecated:** Gap filling is now part of `brownfield-fix`. When editing a file with coverage gaps, `brownfield-fix` automatically triggers gap resolution. Use `brownfield-fix` instead.

## When to use
- dep-graph.json shows `gaps.eventEmitter`, `gaps.dynamic`, or `gaps.conditional` on a file
- brownfield-chat or brownfield-query returns "not mapped" for an important file
- Coverage below 80% on a high-risk file (risk > 50)
- Dev says "this file is not mapped well" or "why doesn't the graph show this dependency"

## When NOT to use
- Asking what a file does → use **brownfield-query** or **brownfield-chat**
- Architecture violations → use **brownfield-drift**
- First-time codebase mapping → use **brownfield-map**

## What to do
1. Run: wednesday-skills fill-gaps --file <file> --min-risk 50
   - This spawns a targeted subagent for that file only
   - Subagent reads: exports list + nearby filenames + gap type
   - Never sends full file source to LLM
   - Returns edges with confidence score
   - Edges below 0.70 confidence are not added — flagged as unknown
2. If dynamic require found with no annotation — ask dev to add:
   // @wednesday-skills:connects-to <event> → <file>
3. If global injection found — ask dev to add:
   // @wednesday-skills:global <name> → <file>
4. After annotation added: run wednesday-skills analyze --incremental
5. Report new coverage % to dev

## Never
- Spawn subagent on files with risk score < 50 — not worth cost
- Send full file source to subagent — exports list and filenames only
- Add edges with confidence below 0.70 to the graph
- Run fill-gaps on the whole codebase at once — file by file only

## Tools
Use Bash tool to run:
- `wednesday-skills fill-gaps --file <file> --min-risk 50`
- `wednesday-skills analyze --incremental`
Use Read tool for:
- `.wednesday/codebase/dep-graph.json` — read `nodes["<file>"].gaps`

## Do NOT use
Do not read the full file source before running fill-gaps.
Do not run fill-gaps without --min-risk flag.

Files in this skill

  • SKILL.md2.4 KB
  • source.json776 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.