perforce-scm

Automate Perforce Helix Core tasks via p4 CLI and P4Python.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/augment-solutions/auggie-skills --skill perforce-scm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perforce-scm
Source: https://github.com/augment-solutions/auggie-skills/tree/main/perforce-scm
Command: npx skills add https://github.com/augment-solutions/auggie-skills --skill perforce-scm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use this skill to automate Perforce (Helix Core) interactions across the p4 CLI and P4Python, handling authentication, workspace management, syncing, editing, changelists, and branching/merging workflows.

Core Features & Use Cases

  • Authentication & connection management (p4 login, P4Python)
  • Workspace / client setup and idempotent management
  • File operations: syncing, editing, adding, deleting, reverting
  • Changelists: creation, submission, shelving, and auditing
  • Branching & merging: streams and classic branches, including merge and integrate workflows
  • MCP integration support: prefer MCP tools when available, with CLI/P4Python as fallback
  • Diagnostics, best practices, and robust error handling patterns
  • References: consult references/branching.md and references/mcp-integration.md for deeper guidance

Quick Start

Create a Perforce workspace, sync the depot to head, edit a file, and submit a new changelist.

Frequently Asked Questions about perforce-scm

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

FAQPage Schema
How do I automate Perforce workspace creation and syncing to head revision?

Automate Perforce workspaces and syncing by using the p4 CLI or P4Python to establish idempotent workspace management, ensuring reliable depot syncs to head without duplicate client setup errors.

Can I use P4Python for changelist creation, shelving, and submission workflows?

P4Python supports changelist workflows by enabling automated creation, file shelving, submission, and auditing, providing robust error handling patterns for reliable Perforce version-control operations.

Does this approach support Perforce streams and classic branching workflows for merging?

Perforce branching and merging workflows support both streams and classic branches, automating integrate and merge operations across Linux and macOS environments with reliable error handling.

What's the best way to handle p4 login and connection management for automated Helix Core tasks?

Handle p4 login and connection management by automating authentication via the p4 CLI and P4Python, establishing secure sessions before executing workspace setup, file operations, or changelist submissions.

Do I need a Perforce MCP server to automate file operations like editing, adding, and reverting?

A Perforce MCP server is optional for automating file operations. The system prefers MCP tools when available, falling back to standard p4 CLI and P4Python methods for editing, adding, and reverting files.

Why does my automated Perforce workflow fail on Linux or macOS during workspace setup?

Automated Perforce workflows on Linux and macOS often fail due to non-idempotent workspace setups. Applying robust error handling patterns and idempotent workspace management ensures reliable execution across environments.