adspecs 0.1.12

package/.adspecs/extensions/.registry

@@ -0,0 +1,30 @@
+{
+  "schema_version": "1.0",
+  "extensions": {
+    "git": {
+      "version": "1.0.0",
+      "source": "local",
+      "manifest_hash": "sha256:9731aa8143a72fbebfdb440f155038ab42642517c2b2bdbbf67c8fdbe076ed79",
+      "enabled": true,
+      "priority": 10,
+      "registered_commands": {
+        "claude": [
+          "adspecs.git.feature",
+          "adspecs.git.validate",
+          "adspecs.git.remote",
+          "adspecs.git.initialize",
+          "adspecs.git.commit"
+        ],
+        "copilot": [
+          "adspecs.git.feature",
+          "adspecs.git.validate",
+          "adspecs.git.remote",
+          "adspecs.git.initialize",
+          "adspecs.git.commit"
+        ]
+      },
+      "registered_skills": [],
+      "installed_at": "2026-05-30T02:44:33.842165+00:00"
+    }
+  }
+}

package/.adspecs/extensions/git/README.md

@@ -0,0 +1,100 @@
+# Git Branching Workflow Extension
+
+Git repository initialization, feature branch creation, numbering (sequential/timestamp), validation, remote detection, and auto-commit for Spec Kit.
+
+## Overview
+
+This extension provides Git operations as an optional, self-contained module. It manages:
+
+- **Repository initialization** with configurable commit messages
+- **Feature branch creation** with sequential (`001-feature-name`) or timestamp (`20260319-143022-feature-name`) numbering
+- **Branch validation** to ensure branches follow naming conventions
+- **Git remote detection** for GitHub integration (e.g., issue creation)
+- **Auto-commit** after core commands (configurable per-command with custom messages)
+
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| `adspecs.git.initialize` | Initialize a Git repository with a configurable commit message |
+| `adspecs.git.feature` | Create a feature branch with sequential or timestamp numbering |
+| `adspecs.git.validate` | Validate current branch follows feature branch naming conventions |
+| `adspecs.git.remote` | Detect Git remote URL for GitHub integration |
+| `adspecs.git.commit` | Auto-commit changes (configurable per-command enable/disable and messages) |
+
+## Hooks
+
+| Event | Command | Optional | Description |
+|-------|---------|----------|-------------|
+| `before_constitution` | `adspecs.git.initialize` | No | Init git repo before constitution |
+| `before_specify` | `adspecs.git.feature` | No | Create feature branch before specification |
+| `before_clarify` | `adspecs.git.commit` | Yes | Commit outstanding changes before clarification |
+| `before_plan` | `adspecs.git.commit` | Yes | Commit outstanding changes before planning |
+| `before_tasks` | `adspecs.git.commit` | Yes | Commit outstanding changes before task generation |
+| `before_implement` | `adspecs.git.commit` | Yes | Commit outstanding changes before implementation |
+| `before_checklist` | `adspecs.git.commit` | Yes | Commit outstanding changes before checklist |
+| `before_analyze` | `adspecs.git.commit` | Yes | Commit outstanding changes before analysis |
+| `before_taskstoissues` | `adspecs.git.commit` | Yes | Commit outstanding changes before issue sync |
+| `after_constitution` | `adspecs.git.commit` | Yes | Auto-commit after constitution update |
+| `after_specify` | `adspecs.git.commit` | Yes | Auto-commit after specification |
+| `after_clarify` | `adspecs.git.commit` | Yes | Auto-commit after clarification |
+| `after_plan` | `adspecs.git.commit` | Yes | Auto-commit after planning |
+| `after_tasks` | `adspecs.git.commit` | Yes | Auto-commit after task generation |
+| `after_implement` | `adspecs.git.commit` | Yes | Auto-commit after implementation |
+| `after_checklist` | `adspecs.git.commit` | Yes | Auto-commit after checklist |
+| `after_analyze` | `adspecs.git.commit` | Yes | Auto-commit after analysis |
+| `after_taskstoissues` | `adspecs.git.commit` | Yes | Auto-commit after issue sync |
+
+## Configuration
+
+Configuration is stored in `.specify/extensions/git/git-config.yml`:
+
+```yaml
+# Branch numbering strategy: "sequential" or "timestamp"
+branch_numbering: sequential
+
+# Custom commit message for git init
+init_commit_message: "[Spec Kit] Initial commit"
+
+# Auto-commit per command (all disabled by default)
+# Example: enable auto-commit after specify
+auto_commit:
+  default: false
+  after_specify:
+    enabled: true
+    message: "[Spec Kit] Add specification"
+```
+
+## Installation
+
+```bash
+# Install the bundled git extension (no network required)
+specify extension add git
+```
+
+## Disabling
+
+```bash
+# Disable the git extension (spec creation continues without branching)
+specify extension disable git
+
+# Re-enable it
+specify extension enable git
+```
+
+## Graceful Degradation
+
+When Git is not installed or the directory is not a Git repository:
+- Spec directories are still created under `specs/`
+- Branch creation is skipped with a warning
+- Branch validation is skipped with a warning
+- Remote detection returns empty results
+
+## Scripts
+
+The extension bundles cross-platform scripts:
+
+- `scripts/bash/create-new-feature.sh` — Bash implementation
+- `scripts/bash/git-common.sh` — Shared Git utilities (Bash)
+- `scripts/powershell/create-new-feature.ps1` — PowerShell implementation
+- `scripts/powershell/git-common.ps1` — Shared Git utilities (PowerShell)

package/.adspecs/extensions/git/commands/adspecs.git.commit.md

@@ -0,0 +1,48 @@
+---
+description: "Auto-commit changes after a adspecs command completes"
+---
+
+# Auto-Commit Changes
+
+Automatically stage and commit all changes after a adspecs command completes.
+
+## Behavior
+
+This command is invoked as a hook after (or before) core commands. It:
+
+1. Determines the event name from the hook context (e.g., if invoked as an `after_prd` hook, the event is `after_prd`; if `before_plan`, the event is `before_plan`)
+2. Checks `.adspecs/extensions/git/git-config.yml` for the `auto_commit` section
+3. Looks up the specific event key to see if auto-commit is enabled
+4. Falls back to `auto_commit.default` if no event-specific key exists
+5. Uses the per-command `message` if configured, otherwise a default message
+6. If enabled and there are uncommitted changes, runs `git add .` + `git commit`
+
+## Execution
+
+Determine the event name from the hook that triggered this command, then run the script:
+
+- **Bash**: `.adspecs/extensions/git/scripts/bash/auto-commit.sh <event_name>`
+- **PowerShell**: `.adspecs/extensions/git/scripts/powershell/auto-commit.ps1 <event_name>`
+
+Replace `<event_name>` with the actual hook event (e.g., `after_prd`, `before_plan`, `after_implement`).
+
+## Configuration
+
+In `.adspecs/extensions/git/git-config.yml`:
+
+```yaml
+auto_commit:
+  default: false          # Global toggle — set true to enable for all commands
+  after_prd:
+    enabled: true          # Override per-command
+    message: "[adspecs] Add specification"
+  after_plan:
+    enabled: false
+    message: "[adspecs] Add implementation plan"
+```
+
+## Graceful Degradation
+
+- If Git is not available or the current directory is not a repository: skips with a warning
+- If no config file exists: skips (disabled by default)
+- If no changes to commit: skips with a message

package/.adspecs/extensions/git/commands/adspecs.git.feature.md

@@ -0,0 +1,67 @@
+---
+description: "Create a feature branch with sequential or timestamp numbering"
+---
+
+# Create Feature Branch
+
+Create and switch to a new git feature branch for the given specification. This command handles **branch creation only** — the spec directory and files are created by the core `__SPECKIT_COMMAND_SPECIFY__` workflow.
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Environment Variable Override
+
+If the user explicitly provided `GIT_BRANCH_NAME` (e.g., via environment variable, argument, or in their request), pass it through to the script by setting the `GIT_BRANCH_NAME` environment variable before invoking the script. When `GIT_BRANCH_NAME` is set:
+- The script uses the exact value as the branch name, bypassing all prefix/suffix generation
+- `--short-name`, `--number`, and `--timestamp` flags are ignored
+- `FEATURE_NUM` is extracted from the name if it starts with a numeric prefix, otherwise set to the full branch name
+
+## Prerequisites
+
+- Verify Git is available by running `git rev-parse --is-inside-work-tree 2>/dev/null`
+- If Git is not available, warn the user and skip branch creation
+
+## Branch Numbering Mode
+
+Determine the branch numbering strategy by checking configuration in this order:
+
+1. Check `.specify/extensions/git/git-config.yml` for `branch_numbering` value
+2. Check `.specify/init-options.json` for `branch_numbering` value (backward compatibility)
+3. Default to `sequential` if neither exists
+
+## Execution
+
+Generate a concise short name (2-4 words) for the branch:
+- Analyze the feature description and extract the most meaningful keywords
+- Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
+- Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
+
+Run the appropriate script based on your platform:
+
+- **Bash**: `.specify/extensions/git/scripts/bash/create-new-feature.sh --json --short-name "<short-name>" "<feature description>"`
+- **Bash (timestamp)**: `.specify/extensions/git/scripts/bash/create-new-feature.sh --json --timestamp --short-name "<short-name>" "<feature description>"`
+- **PowerShell**: `.specify/extensions/git/scripts/powershell/create-new-feature.ps1 -Json -ShortName "<short-name>" "<feature description>"`
+- **PowerShell (timestamp)**: `.specify/extensions/git/scripts/powershell/create-new-feature.ps1 -Json -Timestamp -ShortName "<short-name>" "<feature description>"`
+
+**IMPORTANT**:
+- Do NOT pass `--number` — the script determines the correct next number automatically
+- Always include the JSON flag (`--json` for Bash, `-Json` for PowerShell) so the output can be parsed reliably
+- You must only ever run this script once per feature
+- The JSON output will contain `BRANCH_NAME` and `FEATURE_NUM`
+
+## Graceful Degradation
+
+If Git is not installed or the current directory is not a Git repository:
+- Branch creation is skipped with a warning: `[specify] Warning: Git repository not detected; skipped branch creation`
+- The script still outputs `BRANCH_NAME` and `FEATURE_NUM` so the caller can reference them
+
+## Output
+
+The script outputs JSON with:
+- `BRANCH_NAME`: The branch name (e.g., `003-user-auth` or `20260319-143022-user-auth`)
+- `FEATURE_NUM`: The numeric or timestamp prefix used

package/.adspecs/extensions/git/commands/adspecs.git.initialize.md

@@ -0,0 +1,49 @@
+---
+description: "Initialize a Git repository with an initial commit"
+---
+
+# Initialize Git Repository
+
+Initialize a Git repository in the current project directory if one does not already exist.
+
+## Execution
+
+Run the appropriate script from the project root:
+
+- **Bash**: `.specify/extensions/git/scripts/bash/initialize-repo.sh`
+- **PowerShell**: `.specify/extensions/git/scripts/powershell/initialize-repo.ps1`
+
+If the extension scripts are not found, fall back to:
+- **Bash**: `git init && git add . && git commit -m "Initial commit from Specify template"`
+- **PowerShell**: `git init; git add .; git commit -m "Initial commit from Specify template"`
+
+The script handles all checks internally:
+- Skips if Git is not available
+- Skips if already inside a Git repository
+- Runs `git init`, `git add .`, and `git commit` with an initial commit message
+
+## Customization
+
+Replace the script to add project-specific Git initialization steps:
+- Custom `.gitignore` templates
+- Default branch naming (`git config init.defaultBranch`)
+- Git LFS setup
+- Git hooks installation
+- Commit signing configuration
+- Git Flow initialization
+
+## Output
+
+On success:
+- `[OK] Git repository initialized`
+
+## Graceful Degradation
+
+If Git is not installed:
+- Warn the user
+- Skip repository initialization
+- The project continues to function without Git (specs can still be created under `specs/`)
+
+If Git is installed but `git init`, `git add .`, or `git commit` fails:
+- Surface the error to the user
+- Stop this command rather than continuing with a partially initialized repository

package/.adspecs/extensions/git/commands/adspecs.git.remote.md

@@ -0,0 +1,45 @@
+---
+description: "Detect Git remote URL for GitHub integration"
+---
+
+# Detect Git Remote URL
+
+Detect the Git remote URL for integration with GitHub services (e.g., issue creation).
+
+## Prerequisites
+
+- Check if Git is available by running `git rev-parse --is-inside-work-tree 2>/dev/null`
+- If Git is not available, output a warning and return empty:
+  ```
+  [specify] Warning: Git repository not detected; cannot determine remote URL
+  ```
+
+## Execution
+
+Run the following command to get the remote URL:
+
+```bash
+git config --get remote.origin.url
+```
+
+## Output
+
+Parse the remote URL and determine:
+
+1. **Repository owner**: Extract from the URL (e.g., `github` from `https://github.com/github/spec-kit.git`)
+2. **Repository name**: Extract from the URL (e.g., `spec-kit` from `https://github.com/github/spec-kit.git`)
+3. **Is GitHub**: Whether the remote points to a GitHub repository
+
+Supported URL formats:
+- HTTPS: `https://github.com/<owner>/<repo>.git`
+- SSH: `git@github.com:<owner>/<repo>.git`
+
+> [!CAUTION]
+> ONLY report a GitHub repository if the remote URL actually points to github.com.
+> Do NOT assume the remote is GitHub if the URL format doesn't match.
+
+## Graceful Degradation
+
+If Git is not installed, the directory is not a Git repository, or no remote is configured:
+- Return an empty result
+- Do NOT error — other workflows should continue without Git remote information

package/.adspecs/extensions/git/commands/adspecs.git.validate.md

@@ -0,0 +1,49 @@
+---
+description: "Validate current branch follows feature branch naming conventions"
+---
+
+# Validate Feature Branch
+
+Validate that the current Git branch follows the expected feature branch naming conventions.
+
+## Prerequisites
+
+- Check if Git is available by running `git rev-parse --is-inside-work-tree 2>/dev/null`
+- If Git is not available, output a warning and skip validation:
+  ```
+  [specify] Warning: Git repository not detected; skipped branch validation
+  ```
+
+## Validation Rules
+
+Get the current branch name:
+
+```bash
+git rev-parse --abbrev-ref HEAD
+```
+
+The branch name must match one of these patterns:
+
+1. **Sequential**: `^[0-9]{3,}-` (e.g., `001-feature-name`, `042-fix-bug`, `1000-big-feature`)
+2. **Timestamp**: `^[0-9]{8}-[0-9]{6}-` (e.g., `20260319-143022-feature-name`)
+
+## Execution
+
+If on a feature branch (matches either pattern):
+- Output: `✓ On feature branch: <branch-name>`
+- Check if the corresponding spec directory exists under `specs/`:
+  - For sequential branches, look for `specs/<prefix>-*` where prefix matches the numeric portion
+  - For timestamp branches, look for `specs/<prefix>-*` where prefix matches the `YYYYMMDD-HHMMSS` portion
+- If spec directory exists: `✓ Spec directory found: <path>`
+- If spec directory missing: `⚠ No spec directory found for prefix <prefix>`
+
+If NOT on a feature branch:
+- Output: `✗ Not on a feature branch. Current branch: <branch-name>`
+- Output: `Feature branches should be named like: 001-feature-name or 20260319-143022-feature-name`
+
+## Graceful Degradation
+
+If Git is not installed or the directory is not a Git repository:
+- Check the `SPECIFY_FEATURE` environment variable as a fallback
+- If set, validate that value against the naming patterns
+- If not set, skip validation with a warning

package/.adspecs/extensions/git/config-template.yml

@@ -0,0 +1,62 @@
+# Git Branching Workflow Extension Configuration
+# Copied to .adspecs/extensions/git/git-config.yml on install
+
+# Branch numbering strategy: "sequential" (001, 002, ...) or "timestamp" (YYYYMMDD-HHMMSS)
+branch_numbering: sequential
+
+# Commit message used by `git commit` during repository initialization
+init_commit_message: "[adspecs] Initial commit"
+
+# Auto-commit before/after core commands.
+# Set "default" to enable for all commands, then override per-command.
+# Each key can be true/false. Message is customizable per-command.
+auto_commit:
+  default: false
+  before_clarify:
+    enabled: false
+    message: "[adspecs] Save progress before clarification"
+  before_plan:
+    enabled: false
+    message: "[adspecs] Save progress before planning"
+  before_tasks:
+    enabled: false
+    message: "[adspecs] Save progress before task generation"
+  before_implement:
+    enabled: false
+    message: "[adspecs] Save progress before implementation"
+  before_checklist:
+    enabled: false
+    message: "[adspecs] Save progress before checklist"
+  before_analyze:
+    enabled: false
+    message: "[adspecs] Save progress before analysis"
+  before_taskstoissues:
+    enabled: false
+    message: "[adspecs] Save progress before issue sync"
+  after_constitution:
+    enabled: false
+    message: "[adspecs] Add project constitution"
+  after_prd:
+    enabled: false
+    message: "[adspecs] Add PRD"
+  after_clarify:
+    enabled: false
+    message: "[adspecs] Clarify PRD"
+  after_plan:
+    enabled: false
+    message: "[adspecs] Add implementation plan"
+  after_tasks:
+    enabled: false
+    message: "[adspecs] Add tasks"
+  after_implement:
+    enabled: false
+    message: "[adspecs] Implementation progress"
+  after_checklist:
+    enabled: false
+    message: "[adspecs] Add checklist"
+  after_analyze:
+    enabled: false
+    message: "[adspecs] Add analysis report"
+  after_taskstoissues:
+    enabled: false
+    message: "[adspecs] Sync tasks to issues"

package/.adspecs/extensions/git/extension.yml

@@ -0,0 +1,140 @@
+schema_version: "1.0"
+
+extension:
+  id: git
+  name: "Git Branching Workflow"
+  version: "1.0.0"
+  description: "Feature branch creation, numbering (sequential/timestamp), validation, and Git remote detection"
+  author: adspecs
+  repository: https://gitee.com/yuebon/adspecs
+  license: MIT
+
+requires:
+  adspecs_version: ">=0.2.0"
+  tools:
+    - name: git
+      required: false
+
+provides:
+  commands:
+    - name: adspecs.git.feature
+      file: commands/adspecs.git.feature.md
+      description: "Create a feature branch with sequential or timestamp numbering"
+    - name: adspecs.git.validate
+      file: commands/adspecs.git.validate.md
+      description: "Validate current branch follows feature branch naming conventions"
+    - name: adspecs.git.remote
+      file: commands/adspecs.git.remote.md
+      description: "Detect Git remote URL for GitHub integration"
+    - name: adspecs.git.initialize
+      file: commands/adspecs.git.initialize.md
+      description: "Initialize a Git repository with an initial commit"
+    - name: adspecs.git.commit
+      file: commands/adspecs.git.commit.md
+      description: "Auto-commit changes after a adspecs command completes"
+
+  config:
+    - name: "git-config.yml"
+      template: "config-template.yml"
+      description: "Git branching configuration"
+      required: false
+
+hooks:
+  before_constitution:
+    command: adspecs.git.initialize
+    optional: false
+    description: "Initialize Git repository before constitution setup"
+  before_prd:
+    command: adspecs.git.feature
+    optional: false
+    description: "Create feature branch before PRD"
+  before_clarify:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit outstanding changes before clarification?"
+    description: "Auto-commit before spec clarification"
+  before_plan:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit outstanding changes before planning?"
+    description: "Auto-commit before implementation planning"
+  before_tasks:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit outstanding changes before task generation?"
+    description: "Auto-commit before task generation"
+  before_implement:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit outstanding changes before implementation?"
+    description: "Auto-commit before implementation"
+  before_checklist:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit outstanding changes before checklist?"
+    description: "Auto-commit before checklist generation"
+  before_analyze:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit outstanding changes before analysis?"
+    description: "Auto-commit before analysis"
+  before_taskstoissues:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit outstanding changes before issue sync?"
+    description: "Auto-commit before tasks-to-issues conversion"
+  after_constitution:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit constitution changes?"
+    description: "Auto-commit after constitution update"
+  after_prd:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit PRD changes?"
+    description: "Auto-commit after PRD"
+  after_clarify:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit clarification changes?"
+    description: "Auto-commit after spec clarification"
+  after_plan:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit plan changes?"
+    description: "Auto-commit after implementation planning"
+  after_tasks:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit task changes?"
+    description: "Auto-commit after task generation"
+  after_implement:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit implementation changes?"
+    description: "Auto-commit after implementation"
+  after_checklist:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit checklist changes?"
+    description: "Auto-commit after checklist generation"
+  after_analyze:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit analysis results?"
+    description: "Auto-commit after analysis"
+  after_taskstoissues:
+    command: adspecs.git.commit
+    optional: true
+    prompt: "Commit after syncing issues?"
+    description: "Auto-commit after tasks-to-issues conversion"
+
+tags:
+  - "git"
+  - "branching"
+  - "workflow"
+
+config:
+  defaults:
+    branch_numbering: sequential
+    init_commit_message: "[adspecs] Initial commit"

package/.adspecs/extensions/git/git-config.yml

@@ -0,0 +1,62 @@
+# Git Branching Workflow Extension Configuration
+# Copied to .specify/extensions/git/git-config.yml on install
+
+# Branch numbering strategy: "sequential" (001, 002, ...) or "timestamp" (YYYYMMDD-HHMMSS)
+branch_numbering: sequential
+
+# Commit message used by `git commit` during repository initialization
+init_commit_message: "[adspecs] Initial commit"
+
+# Auto-commit before/after core commands.
+# Set "default" to enable for all commands, then override per-command.
+# Each key can be true/false. Message is customizable per-command.
+auto_commit:
+  default: false
+  before_clarify:
+    enabled: false
+    message: "[adspecs] Save progress before clarification"
+  before_plan:
+    enabled: false
+    message: "[adspecs] Save progress before planning"
+  before_tasks:
+    enabled: false
+    message: "[adspecs] Save progress before task generation"
+  before_implement:
+    enabled: false
+    message: "[adspecs] Save progress before implementation"
+  before_checklist:
+    enabled: false
+    message: "[adspecs] Save progress before checklist"
+  before_analyze:
+    enabled: false
+    message: "[adspecs] Save progress before analysis"
+  before_taskstoissues:
+    enabled: false
+    message: "[adspecs] Save progress before issue sync"
+  after_constitution:
+    enabled: false
+    message: "[adspecs] Add project constitution"
+  after_prd:
+    enabled: false
+    message: "[adspecs] Add PRD"
+  after_clarify:
+    enabled: false
+    message: "[adspecs] Clarify PRD"
+  after_plan:
+    enabled: false
+    message: "[adspecs] Add implementation plan"
+  after_tasks:
+    enabled: false
+    message: "[adspecs] Add tasks"
+  after_implement:
+    enabled: false
+    message: "[adspecs] Implementation progress"
+  after_checklist:
+    enabled: false
+    message: "[adspecs] Add checklist"
+  after_analyze:
+    enabled: false
+    message: "[adspecs] Add analysis report"
+  after_taskstoissues:
+    enabled: false
+    message: "[adspecs] Sync tasks to issues"