/ase-repo-task

name: ase-repo-task
argument-hint: "[--help|-h] [--focus|-f <section>[,...]] [--staged] [--unstaged] [--branch|-b <branch>] [--commit|-c <commit>] [<task-id>[:]] [<scope>]"
description: >
    Derive a new task plan from a Git change set -- the staged changes
    (or, with `--unstaged`, the unstaged and untracked changes, with
    `--branch`, a branch against its base, or, with `--commit`, a single
    commit) -- optionally narrowed to a scope topic, by filling its
    SPECIFICATION (WHAT), DESIGN (HOW), and VERIFICATION (WHEN) sections
    (or only the focused ones), so that a re-implementation of the task,
    e.g. after an export to a foreign issue tracker, yields a similar
    change set. Use when the user wants a change set, branch, or commit
    "turned into", "described as", or "reverse-engineered into" a "task",
    "plan", or "issue".
user-invocable: true
disable-model-invocation: false
effort: high
allowed-tools:
    - "Bash(git diff *)"
    - "Bash(git ls-files *)"
    - "Bash(git rev-parse *)"
    - "Bash(git for-each-ref *)"
    - "Bash(git rev-list *)"
    - "Bash(git merge-base *)"
    - "Bash(git branch *)"
    - "Bash(git worktree list *)"
    - "Bash(git show *)"
    - "Bash(git log *)"
    - "Bash(git grep *)"
    - "Bash(git ls-tree *)"
    - "Bash(git -C *)"

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md

<purpose name="ase-repo-task"> Derive a Task from a Change Set </purpose>

<expand name="getopt" arg1="ase-repo-task" arg2="--focus|-f=(all|SPECIFICATION|SPEC|WHAT|DESIGN|DES|HOW|VERIFICATION|VERIFY|VER|WHEN)... --staged --unstaged --branch|-b= --commit|-c="> $ARGUMENTS </expand>

<objective> *Reverse-engineer* a Git change set -- optionally narrowed to a scope topic -- into a *new task plan*, whose `SPECIFICATION (WHAT)` is *exactly precise*, whose `DESIGN (HOW)` captures at least the *major cruxes*, and whose `VERIFICATION (WHEN)` is *decent*, so that an independent re-implementation of the task yields a *similar* change set. </objective>

@${CLAUDE_SKILL_DIR}/../../meta/ase-format-task.md @${CLAUDE_SKILL_DIR}/../../meta/ase-common-task.md

Procedure ---------

This skill *never* modifies any artifact of the working copy: it only reads the change set and the project files, and persists the new task plan exclusively via the `ase_task_save` MCP tool.

1. **Determine Task and Scope:**

1. Set <instruction><getopt-arguments/></instruction>, with any leading and trailing whitespace stripped, and set <new-task-id></new-task-id> and <scope></scope> (both empty). Inherit the always existing <ase-session-id/> from the current context. Do not output anything.

<expand name="task-focus" arg1="ase-repo-task"></expand>

2. React on the task id and the scope:

<if condition=" <instruction/> matches the regexp `^[a-zA-Z0-9#][a-zA-Z0-9#_-]*:?$` "> The lone token is the *task id* (with an optional and ignored trailing `:`), never a scope. Set <new-task-id/> to <instruction/>, with any trailing `:` stripped. </if> <elseif condition=" <instruction/> has the format `<id/>: <text/>` where <id/> matches the regexp `^[a-zA-Z0-9#][a-zA-Z0-9#_-]*$` "> Set <new-task-id><id/></new-task-id> and <scope><text/></scope>, with any leading and trailing whitespace stripped. </elseif> <else> No task id was given, so a new one is allocated in step 5. Set <scope><instruction/></scope>. </else>

<if condition="<scope/> is not empty"> Only output the following <template/>:

<template> ⧉ **ASE**: ✪ skill: **ase-repo-task**, ⌕ scope: **<scope/>** </template> </if>

3. <if condition="<new-task-id/> is not empty"> *Detect a target collision*, strictly *before* any further work: call the `ase_task_list(verbose: false)` tool of the `ase` MCP server and check the `id` fields of the returned `tasks` array. Do not output anything related to this MCP tool call. If <new-task-id/> is already present, only output the following <template/> and then immediately *STOP* processing the entire current skill, leaving the existing task plan untouched:

<template> ⧉ **ASE**: ◉ task: **<new-task-id/>**, ▶ status: **target exists** </template>

Directly *after* this <template/>, and *before* stopping, give the corrective hint by expanding the following (which, depending on the configured <ase-guidance-level/>, may expand into nothing and hence emit no output at all):

<ase-tpl-hint level="minimal"> Use `/ase-task-delete <new-task-id/>` to delete the existing task plan first, or choose another task id. </ase-tpl-hint> </if>

2. **Determine Change Set:**

1. <if condition="<getopt-option-commit/> is not empty and (<getopt-option-branch/> is not empty or <getopt-option-staged/> is equal `true` or <getopt-option-unstaged/> is equal `true`)"> Only output the following <template/> and then *STOP* immediately:

<template> ⧉ **ASE**: ✪ skill: **ase-repo-task**, ▶ ERROR: option `--commit` cannot be combined with `--branch`, `--staged`, or `--unstaged` </template> </if>

Set <changes/> to the *uncommitted* changes to derive from: to `staged and unstaged` if both <getopt-option-staged/> and <getopt-option-unstaged/> are equal `true`, to `staged` if only <getopt-option-staged/> is equal `true`, to `unstaged` if only <getopt-option-unstaged/> is equal `true`, and to empty otherwise. Here, the `unstaged` changes always include the *untracked* files.

2. <if condition="<getopt-option-branch/> is not empty"> Determine the *