aep-git-ref

Guide AEP-specific git worktree workflows with branch naming and commit patterns.

Updated May 18, 2026
One-click install
npx skills add https://github.com/memorysaver/project-understanding --skill aep-git-ref
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aep-git-ref
Source: https://github.com/memorysaver/project-understanding/tree/main/.agents/skills/aep-git-ref
Command: npx skills add https://github.com/memorysaver/project-understanding --skill aep-git-ref

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to AEP-specific git and git worktree workflows, offering solutions for common issues and best practices in parallel agent isolation.

Core Features & Use Cases

  • AEP Branch Naming Conventions: Defines the conventions for branch naming, including feature, migration, hotfix, and migration project branches.
  • One-Commit-per-Task Pattern: Implements a convention where each task in a feature branch results in a single commit, enhancing reviewability and maintainability.
  • Control-Plane Commits: Details the process for commits made by control-plane operations such as /aep-dispatch, /aep-envision, and /aep-wrap.

Quick Start

To create a new feature worktree, run the following command:

git worktree add -b feat/<name> .feature-workspaces/<name> "$BASE"

Frequently Asked Questions about aep-git-ref

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

FAQPage Schema
How do I manage parallel agent isolation using git worktree?▼

Git worktree enables parallel agent isolation by creating separate working directories linked to the same repository. This Skill provides AEP-specific workflows for branch naming and control-plane commits to manage those isolated environments effectively.

What is the one-commit-per-task pattern in git feature branches?▼

The one-commit-per-task pattern is a git convention where each task within a feature branch results in a single commit. This approach enhances code reviewability and maintainability for AEP-specific development workflows.

How do I create a new feature worktree for AEP workflows?▼

To create a feature worktree, run `git worktree add -b feat/<name> .feature-workspaces/<name> "$BASE"`. This command sets up an isolated branch directory for AEP-specific parallel agent tasks.

What branch naming conventions should I use for AEP git workflows?▼

AEP git workflows define specific branch naming conventions for feature, migration, and hotfix branches. These conventions organize parallel agent tasks and control-plane operations into a standardized structure.

How do control-plane commits work in AEP git workflows?▼

Control-plane commits in AEP workflows are generated by specific operations like `/aep-dispatch`, `/aep-envision`, and `/aep-wrap`. This Skill details the process for managing these automated commits within the worktree structure.

Does this git worktree workflow require specific AEP tools to function?▼

The workflow targets users involved in AEP workflows requiring git worktree management and parallel agent isolation. It assumes familiarity with AEP operations like `/aep-dispatch` and standard git version control commands.