Skip to main content
Change proposals are one of two ways to update your playbook. Unlike direct updates, change proposals require team review before changes are applied.
Private Beta — Change Proposals is currently in private beta. Contact Packmind to get access to this feature.
Change Proposals require CLI version 0.21.0 or later. Run packmind-cli --version to check your version, and see CLI Installation to upgrade.

​
What are Change Proposals?

Change Proposals enable users to propose modifications to distributed artifacts (standards, commands, skills) directly from their local environment. Once submitted, proposals are reviewed and approved through the Packmind UI, ensuring that changes go through a controlled review process before being applied. There are two ways to submit change proposals:
  1. Use the packmind-update-playbook skill — the skill analyzes your coding session, identifies relevant changes, and submits proposals on your behalf automatically. This is the recommended approach.
  2. Edit local files manually and use the CLI — modify distributed artifact files directly, then use packmind-cli diff commands to preview and submit your changes.

​
Submitting Changes with the packmind-update-playbook Skill

The packmind-update-playbook skill automates the entire process. It analyzes your coding session, identifies what changed, and submits change proposals on your behalf. It follows a four-phase workflow:
  1. Summarize the session — extracts what was built, what patterns emerged, and what decisions were made.
  2. Analyze existing artifacts — evaluates your current standards, commands, and skills against the session context.
  3. Propose a change report — presents a numbered list of proposed updates, new artifacts, or deprecations for you to approve.
  4. Apply approved changes — edits local files and submits proposals for review on Packmind.
The skill activates automatically when you use phrases like “update the playbook”, “sync standards”, or “check if we need new standards”. It can also be triggered after coding sessions where new patterns or conventions emerged.
Learn more about how skills work in the Skills Management section.

​
Submitting Changes with the CLI

The CLI requires a git repository with a remote configured. If no git repository or remote is detected, the command will fail with an error. Make sure you also have the CLI installed and configured — see CLI setup for details.
Local changes must be made on files deployed by Packmind during distribution — these include files in the .packmind/ directory as well as agent-specific directories such as .claude/, .github/, .cursor/, and others depending on your enabled AI agents (see Distribute artifacts for the full list).

​
View local changes

To see what local changes haven’t been submitted yet: 
packmind-cli diff

​
Submit changes

To submit your local changes as a proposal with a justification message: 
packmind-cli diff --submit -m "Clarify error handling rules for API endpoints"
The message is required when submitting and has a maximum length of 1024 characters. If you omit the -m flag in interactive mode, an editor will open for you to write the message.
If you see an error like Failed to submit "": is outdated, please run packmind-cli install to update it, it means the local artifact version is stale. Run packmind-cli install to fetch the latest versions, reapply your changes, and submit again.

​
Include already-submitted changes

To view all local changes, including those that have already been submitted: 
packmind-cli diff --include-submitted

​
Add new artifacts

To submit a new artifact (standard, command, or skill) as a change proposal: 
packmind-cli diff add <path> -m "Description of the new artifact"
The file must be located in a recognized artifact directory:
Artifact typeRecognized directories
Commands.claude/commands/, .cursor/commands/, .github/prompts/, .continue/prompts/, .packmind/commands/
Standards.claude/rules/, .cursor/rules/, .github/instructions/, .continue/rules/, .packmind/standards/
Skills.claude/skills/, .cursor/skills/, .github/skills/

​
File format requirements

  • Commands: File must not be empty. Frontmatter with name: is optional.
  • Standards: Must contain a heading and at least one rule (bullet point).
  • Skills: Path must point to a directory containing a SKILL.md with valid frontmatter (name, description) and a non-empty body.

​
When it won’t work

The command will fail if:
  • The file is not inside a recognized artifact directory
  • The path points to a directory instead of a file (for commands and standards)
  • The file content is invalid (empty command, standard without rules, skill missing SKILL.md)

​
Message flag

The -m "message" flag is required in non-interactive or CI mode. If omitted in interactive mode, an editor will open. Maximum length is 1024 characters. On success, the artifact is submitted as a change proposal visible in the Review changes UI, with a summary logged to the console.

​
Remove artifacts

To suggest removing an artifact (standard, command, or skill) from packages: 
packmind-cli diff remove <path> -m "Reason for removing the artifact"
The file must be located in a recognized artifact directory (same as for adding new artifacts). The -m flag follows the same rules as other diff commands.

​
What happens on success

  • The file is deleted locally
  • A removal proposal is created and appears in the Review changes UI

​
When it won’t work

The command will fail if the artifact was not deployed by Packmind (error: “This does not come from Packmind”).

​
Reviewing removal proposals

Removal proposals appear alongside other change proposals in the Review changes UI. The reviewer can either dismiss the proposal or choose Remove from packages. When removing, a dialog lets the reviewer select which packages to remove the artifact from, showing which packages are affected before applying the change.

​
Conflicts with removal proposals

If someone submits a modification and someone else submits a removal for the same artifact, both proposals appear in the review UI. Accepted removal proposals block conflicting proposals on the same artifact.

​
Important: Pending Changes and the Install Command

While changes are pending (not yet accepted), running packmind-cli install will overwrite your local modifications with the server version. This will erase any unsubmitted changes.
Always submit your changes before running packmind-cli install to avoid losing your work.

​
Reviewing Change Proposals in the UI

Once changes have been submitted, they can be reviewed in the Packmind web interface:
  1. Navigate to the Review changes module from the sidebar menu
  2. Proposals are grouped by artifact (standard, command, or skill)
  3. Each proposal shows the modification type and a diff view highlighting additions and removals
  4. Review each proposal and choose to accept or dismiss it
  5. Click Apply changes to create a new version of the artifact with the accepted changes

​
Conflict Management

If a new version of an artifact is published while a change proposal is still pending, the proposal becomes outdated. Packmind detects this conflict automatically — the proposal will be marked as conflicting and cannot be applied as-is. The submitter needs to rebase their changes on the latest version and submit a new proposal.