ase-arch-analyze
FreeReview software architecture, including package cohesion and inter-package coupling
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
@${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>No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review software architecture, including package cohesion and inter-package coupling
The English summary is being prepared. Showing the original description.
Discover additional, third-party components (libraries/frameworks) for the technology stack to provide needed functionality.
The English summary is being prepared. Showing the original description.
Analyze the source code for problems in either the logic and semantics and its related control flow, performance and efficiency, or security.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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?"
The English summary is being prepared. Showing the original description.
Give insights into the source code.
The English summary is being prepared. Showing the original description.