Review software architecture, including package cohesion and inter-package coupling
中文简介正在准备中。当前显示原文说明。
Resolve the Git merge conflicts of a working directory -- of an in-progress merge, rebase, cherry-pick, revert, stash apply, or of conflict markers left by patch -- carefully and semantically, never losing any change, escalate unresolvable hunks as-is, continue the in-progress operation, and emit a RESOLVED, PARTIAL, NONE, or FAILED verdict. Use when the user calls to "resolve" or "fix" merge conflicts.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
@${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-repo-resolve"> Resolve Merge Conflicts </purpose><expand name="getopt" arg1="ase-repo-resolve" arg2="--dir|-d=. --safe|-s --interactive|-i"> $ARGUMENTS </expand>
<objective> *Resolve* the merge conflicts of the working directory *semantically*, *never* losing any change, *escalate* the unresolvable hunks as-is, *continue* the in-progress operation, and report the *resolve verdict*. </objective>@${CLAUDE_SKILL_DIR}/../../meta/ase-common-resolve.md
Set <paths/> to <getopt-arguments/> with any leading and trailing whitespace stripped. Do not output anything.
Resolve the conflicts by expanding the following:
<expand name="resolve-conflicts" arg1="ase-repo-resolve" arg2="<getopt-option-dir/>" arg3="<getopt-option-interactive/>" arg4="<getopt-option-safe/>" arg5="<paths/>"></expand>
If <resolve-verdict/> is not RESOLVED or <resolve-operation/>
is none, skip this entire STEP 2, as either conflicts remain
or there is no operation to continue (e.g., after
git stash apply or patch --merge).
Run the command
git -C "<repo-root/>" diff --name-only --diff-filter=U. If its
output is not empty (unmerged files outside of <paths/>
remain), only output the following <template/> and skip the
remaining items of this STEP 2:
Continue the operation by running the command
git -C "<repo-root/>" -c core.editor=true <resolve-operation/> --continue,
which keeps the prepared commit message without opening an
editor.
Report the escalations by expanding the following:
<expand name="resolve-report" arg1="ase-repo-resolve"></expand>
Only output the following <template/>:
<template> ⧉ **ASE**: ✪ skill: **ase-repo-resolve**, ⎇ operation: **<resolve-operation/>**, ▶ RESOLVE VERDICT: **<resolve-verdict/>** </template>还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Review software architecture, including package cohesion and inter-package coupling
中文简介正在准备中。当前显示原文说明。
Discover additional, third-party components (libraries/frameworks) for the technology stack to provide needed functionality.
中文简介正在准备中。当前显示原文说明。
Analyze the source code for problems in either the logic and semantics and its related control flow, performance and efficiency, or security.
中文简介正在准备中。当前显示原文说明。
Edit Source Code: Use when the user wants to "edit" the code base in one shot from a query or a bare analyzer issue id like "P1", fusing crafting, refactoring, and resolving with optional grilling, verification, looping, and Git worktree isolation.
中文简介正在准备中。当前显示原文说明。
Explains code with WHAT, WHY, ANALOGY, DIAGRAM, CRUXES, and GOTCHAS. Use when you want to know how code works or when the user asks "how does this work?"
中文简介正在准备中。当前显示原文说明。
Give insights into the source code.
中文简介正在准备中。当前显示原文说明。