agentleFS
Sign inStart free
forcedotcomforcedotcom/salesforcedx-vscode/.agents/skills/vscode-extension-launch/SKILL.md

vscode-extension-launch

Skill1k starsChanged 25 days agoBSD-3-ClauseView on GitHub

Maintain this repository's VS Code extension launch configs when adding or removing extension packages, changing launch groups, or adding subset debug configurations.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about forcedotcom/salesforcedx-vscode

The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 52

Talked about on GitHub and Stack Overflow (52 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before changing extension packages or extension-host launch configurations, read these related files:

    line 8
  2. Very specific:

    When removing an extension, check scripts/extension-groups.json for references to its package directory name.

    line 15
  3. Very specific:

    Verify that each extension-host launch config's preLaunchTask exists, the intended group resolves to real extension packages, and any …

    line 21
  4. Very specific:

    Run pnpm run check:extension-launch after changing an extension package, group, picker task, or extension-host launch configuration.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

VS Code extension launches

Before changing extension packages or extension-host launch configurations, read these related files:

  • .vscode/launch.json for debug configurations and their preLaunchTask values.
  • .vscode/tasks.json for build and selection task order.
  • scripts/extension-groups.json for named subsets.
  • scripts/selectedExtensions.mjs and scripts/pickExtensions.mjs for discovery, dependency expansion, and the generated selection directory.

When removing an extension, check scripts/extension-groups.json for references to its package directory name. Update any affected group, then check the corresponding tasks and launch configurations. Also check whether its removal changes another extension's declared extensionDependencies.

When adding a launch configuration for a subset, add a named group in scripts/extension-groups.json and have a prelaunch task call scripts/pickExtensions.mjs --group <name>. Pass --extensionDevelopmentPath=${workspaceFolder}/.vscode/selected-extensions and one --disable-extension=salesforce.<package> per monorepo extension so installed copies of unselected extensions stay off while other installed extensions still load. The launch check fails when that list drifts from packages/. Keep the selected package list out of launch.json; the picker creates the links for the selected group. The generated directory is ignored by Git and should not be committed.

Preserve build behavior when changing launch configs. Configurations that previously built must still run the full Compile and Bundle task. For build-enabled extension launches, use dependsOrder: "sequence" with Compile and Bundle before the picker task. Selecting a subset controls what launches, not what gets built. Keep the broad outFiles patterns for source maps unless there is a concrete reason to change them.

Verify that each extension-host launch config's preLaunchTask exists, the intended group resolves to real extension packages, and any build-enabled task reaches Compile and Bundle before selection. Run pnpm run check:extension-launch after changing an extension package, group, picker task, or extension-host launch configuration. This check also runs in the repository's test and precommit workflows.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free