packaging-2gp

Automate Salesforce 2GP packaging workflows with sfdx configuration and versioning.

2|Updated Mar 18, 2026

Search Tags:#versioning #deployment #packaging #salesforce #ancestry #2gp

Ready to run

npx skills add https://github.com/bhanu91221/claude-sfdx-iq --skill packaging-2gp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: packaging-2gp
Source: https://github.com/bhanu91221/claude-sfdx-iq/tree/main/skills/packaging-2gp
Command: npx skills add https://github.com/bhanu91221/claude-sfdx-iq --skill packaging-2gp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Second-generation packaging for Salesforce can be complex, involving setup, versioning, ancestry, and ISV distribution. This Skill helps teams manage 2GP lifecycles consistently.

Core Features & Use Cases

End-to-end 2GP lifecycle: from project configuration to package distribution across environments.
Versioning and Ancestry: manage version numbers, ancestry relationships, and upgrade paths.
Namespace and distribution strategy: supports unlocked and managed packages, including AppExchange distribution.
Use Case: A DevOps team standardizes packaging for multiple Salesforce modules with automated checks and release notes.

Quick Start

Initialize a 2GP project with sfdx, define package directories, and enable versioning and ancestry governance to start packaging.

Frequently Asked Questions about packaging-2gp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Salesforce 2GP packaging workflows for versioning and distribution?▼

Salesforce 2GP packaging workflows are automated by configuring sfdx project directories, defining namespace considerations, and enabling versioning and ancestry governance to manage modular package distribution across orgs and sandboxes.

What is the best way to manage versioning and ancestry relationships for Salesforce unlocked packages?▼

Managing versioning and ancestry for Salesforce unlocked packages involves defining version numbers and ancestry relationships within sfdx configurations to establish clear upgrade paths and package lifecycle governance across environments.

Can I use sfdx to orchestrate metadata for both managed and unlocked Salesforce packages?▼

Yes, sfdx orchestrates metadata for both managed and unlocked Salesforce packages by enforcing dependency handling, promotion rules, and namespace strategy to support modular ISV distribution across orgs and sandboxes.

When do I need to configure package ancestry and namespace considerations for Salesforce AppExchange distribution?▼

Package ancestry and namespace considerations are required for Salesforce AppExchange distribution when managing managed packages that need defined upgrade paths, dependency handling, and consistent lifecycle task governance across ISV environments.

Does Salesforce 2GP packaging support dependency handling and promotion rules for DevOps release standardization?▼

Yes, Salesforce 2GP packaging supports dependency handling and promotion rules to help DevOps teams standardize packaging for multiple modules with automated checks and release notes across environments.