Skip to content

Add remove-template skill for Package repository#326

Merged
wmathurin merged 3 commits into
forcedotcom:devfrom
wmathurin:add-remove-template-skill
Apr 10, 2026
Merged

Add remove-template skill for Package repository#326
wmathurin merged 3 commits into
forcedotcom:devfrom
wmathurin:add-remove-template-skill

Conversation

@wmathurin
Copy link
Copy Markdown
Contributor

@wmathurin wmathurin commented Apr 10, 2026

Summary

Add comprehensive skills for the Package repository:

  1. remove-template.md: Process for updating Package repo after template removal
  2. test-templates.md: Using test_force.js to test templates and CLI tools

Skills Content

remove-template.md

Documents the process for updating the Package repository after a template has been removed from the Templates repository:

  • setup_test_branches.js: Update hardcoded templatesPackageJsons array
  • constants.js checks: Handle default template mappings in appTypesToPath
  • AppType removal workflow (if removing last template of an appType):
    • Remove appType from CLI definitions
    • Update test_force.js APP_TYPE enum
    • Regenerate OCLIF commands
    • Regenerate SFDX plugin README
  • Search for explicit references: Grep all JS files for template name
  • Documentation updates: README.md and CLAUDE.md

test-templates.md

Documents using test_force.js to test templates and CLI tools:

  • Testing with default or custom template sources
  • Overriding template source branches via --templaterepouri
  • Overriding SDK dependencies via --sdkdependencies
  • Testing all CLIs or specific CLIs
  • Cross-repo testing scenarios (templates + package changes)
  • Performance notes and validation checklists

Purpose

These skills are part of the coordinated template removal and testing workflow across the Mobile SDK ecosystem. They ensure that when templates are removed or modified, the Package repository (which contains CLI tools and release scripts) is properly updated and tested.

Related Skills

  • SalesforceMobileSDK-Templates/.claude/skills/remove-template.md
  • SalesforceMobileSDK-Templates/.claude/skills/test-template.md
  • SalesforceMobileSDK-UITests/.claude/skills/remove-template.md
  • SalesforceMobileSDK-Workspace/.claude/skills/remove-template.md (orchestration)
  • SalesforceMobileSDK-Workspace/.claude/skills/test-templates.md (orchestration)

Note

This PR is based on dev branch. There are changes in the diff from PR #325 (automatic prompt skipping) that will be resolved via rebase after #325 is merged.

This skill documents the process for updating the Package repository
after a template has been removed from the Templates repository:
- Update setup_test_branches.js (templatesPackageJsons array)
- Check constants.js for default templates
- If last template of appType, remove appType support
- Update test_force.js APP_TYPE enum
- Regenerate OCLIF commands and SFDX README
- Search all JS files for references
- Update README.md and CLAUDE.md

Part of the template removal workflow across the Mobile SDK ecosystem.
This skill documents using test_force.js to test templates:
- Testing CLI tools with default or custom template sources
- Overriding template source branches
- Overriding SDK dependencies
- Testing all CLIs or specific CLIs
- Cross-repo testing scenarios

Part of the template testing workflow across the Mobile SDK ecosystem.
@brandonpage
Copy link
Copy Markdown
Contributor

So when the native template is removed from forcedroid does it make sense to rename native_kotlin? I assume the answer is no, but I want to double check while we are reviewing trailhead docs since that would affect the challenge.

@wmathurin
Copy link
Copy Markdown
Contributor Author

So when the native template is removed from forcedroid does it make sense to rename native_kotlin? I assume the answer is no, but I want to double check while we are reviewing trailhead docs since that would affect the challenge.

We could, but for now I just left it as is.

Added step 3.4 to link the sfdx plugin after regenerating OCLIF
commands. This ensures the plugin reflects the changes made to
constants.js. Also updated validation checklist.
@wmathurin wmathurin merged commit 398794e into forcedotcom:dev Apr 10, 2026
13 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants