/ase-code-resolve

name: ase-code-resolve
argument-hint: "[--help|-h] [--auto|-a] [--dry|-d] [--quick|-Q] [--next|-n <option>[,...]] [<task-id>:] <problem>"
description: >
    Resolve Problem:
    Use when user wants to "bugfix" or "fix" code or "resolve" a problem.
user-invocable: true
disable-model-invocation: false
effort: xhigh
allowed-tools:
    - "Skill"
    - "Agent"

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

<purpose name="ase-code-resolve"> Resolve Problem </purpose>

<expand name="getopt" arg1="ase-code-resolve" arg2="--auto|-a --dry|-d --quick|-Q --next|-n=(none|DONE|EDIT|GRILL|PREFLIGHT|IMPLEMENT)..."> $ARGUMENTS </expand>

<if condition="<getopt-option-quick/> is equal `true`"> The `--quick`/`-Q` flag is a *shorthand alias*: set <getopt-option-auto/> to `true`, <getopt-option-dry/> to `true`, and <getopt-option-next/> to `IMPLEMENT,DELETE`. Do not output anything. </if>

<objective> *Resolve* the following problem: <problem><getopt-arguments/></problem> </objective>

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

Procedure ---------

You *MUST* *NOT* call `Edit`, `Write`, `NotebookEdit`, or any filesystem-modifying tool during this entire skill. The *only* permitted way to persist artifacts is via `ase_task_save(...)`.

<flow>

1. <step id="STEP 1: Reason About Problem">

1. If <problem/> matches the regexp `^[PT]\d+$` (i.e. a bare issue identifier like `P1`, `P2`, `T1`, `T2`, ...), set <problem-id><problem/></problem-id> and <ase-task-id><problem/></ase-task-id>, then call the `ase_kv_get(key: "ase-issue-<problem-id/>")` tool of the `ase` MCP server to retrieve the previously persisted problem description. If the returned `text` is non-empty, set <problem><text/></problem> and call the `ase_task_id(id: "<ase-task-id/>", session: "<ase-session-id/>")` tool from the `ase` MCP server to implicitly switch the task, otherwise complain to the user that no analyzer result exists for <problem-id/> and stop processing.

2. <if condition=" <problem-id/> is not set AND <problem/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$` "> Set <ase-task-id><problem/></ase-task-id> (set task id to problem) and <problem></problem> (set problem empty), call the `ase_task_id(id: "<ase-task-id/>", session: "<ase-session-id/>")` tool from the `ase` MCP server to switch the task, and then only output the following <template/>:

<template> ⧉ **ASE**: ◉ task: **<ase-task-id/>**, ▶ status: **task given** </template> </if>

3. <if condition=" <problem-id/> is not set AND <problem/> has the format `<id/>: <text/>` AND <id/> matches the regexp `^[a-zA-Z][a-zA-Z0-9_-]*$` "> Set <problem><text/></problem> and <ase-task-id><id/></ase-task-id> and call the `ase_task_id(id: "<ase-task-id/>", session: "<ase-session-id/>")` tool from the `ase` MCP server to implicitly switch the task. Do not output anything. </if>

4. <if condition="<problem/> is empty"> Ask the user interactively, without a special tool, for the initial problem with a single question:

`**No problem details known yet. What is the problem you want to resolve?**`

Then set <problem/> to the response of the user. </if>

5. <if condition=" <ase-task-id/> is equal `default` and <problem/> is not empty "> Set <ase-task-id/> to a unique task id, derived from <problem/>, which consists of two lower-case words concatenated with a `-` character. Then call the `ase_task_id(id: "<ase-task-id/>", session: "<ase-session-id/>")` tool from the `ase` MCP server to implicitly switch the task. Do not output anything. </if>

6. Report the task and problem with the following <template/>:

<template> ⧉ **ASE**: ◉ task: **<ase-task-id/>** ⧉ **ASE**: ⇌ problem: **<problem/>** </template>

7. Figure out what the requested <problem/> is about.

8. Ask the user for clarification if the goal of this resolution is too unclear.

9. Do not output anything else in this step, unless you asked the user.

10. Investigate and *figure out details* related to this problem. Report those details with the following <template/>:

<template> <ase-tpl-bullet-signal/> **PROBLEM CONTEXT**: *<context/>* <affected-code-excerpt/> <optional-diagram/>

<ase-tpl-bullet-signal/> **PROBLEM DETAILS**: *<summary/>* ● [...] ● [...] ● [...] </template>

Hints:

• Give a short one-sentence <context/> of the <problem/> plus

a short excerpt of the affected code <affected-code-excerpt/>.

• Give a short one-sentence <summary/> of the <problem/> plus *precise*

but *brief* code processing information to understand the problem. Try to keep the number of bullet points (●) in the range of 1-4.

• In case of a *complex context situation* with complex *structure*

(layout, components, dependencies, etc), complex *control flow* (branching, concurrency, etc), complex *state machine* (states, transitions, etc), complex *data flow* (actors, messages, etc), or complex *data structure* (classes, entities, relationships, etc), visualize it with an optional diagram <optional-diagram/> by building a Mermaid specification <mermaid-spec/> (e.g. `flowchart TB`, `stateDiagram-v2`, `sequenceDiagra