Token导航 LogoToken导航

Agent Skill · 研究检索

kata-remove-phase(卡塔移除阶段)

kata-remove-phase 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

kata-remove-phase 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 56,650。

总安装 447周安装 19GitHub Stars 1下载 157核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:kata-remove-phase(卡塔移除阶段)
来源仓库:https://github.com/gannonh/kata-skills
仓库路径:skills/kata-remove-phase
安装命令:
npx skills add https://github.com/gannonh/kata-skills --skill kata-remove-phase
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/gannonh/kata-skills --skill kata-remove-phase

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

kata-remove-phase 用于查找、检索和筛选相关信息。适合在关键词、任务场景或来源线索下快速定位候选结果。通过 npx skills add 命令从 gannonh/kata-skills 仓库安装。安装前应确认权限范围、维护状态及是否触发联网或文件操作。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/kata-remove-phase

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/gannonh/kata-skills --skill kata-remove-phase;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

kata-remove-phase 怎么安装?

在终端执行 npx skills add https://github.com/gannonh/kata-skills --skill kata-remove-phase。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

kata-remove-phase 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

kata-remove-phase 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

kata-remove-phase 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

kata-remove-phase 用的人多吗?

公开数据是累计安装 447 次,近一周安装 19 次,下载 157 次,GitHub 1 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

kata-remove-phase 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
kata-remove-phase

卡塔移除阶段 · 本页

4471只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Purpose: Clean removal of work you've decided not to do, without polluting context with cancelled/deferred markers. Output: Phase deleted, all subsequent phases renumbered, git commit as historical record.

<execution_context> @.planning/ROADMAP.md @.planning/STATE.md </execution_context>

If no argument provided:

ERROR: Phase number required
Usage: /kata-remove-phase <phase-number>
Example: /kata-remove-phase 17

Exit.

If ROADMAP.md exists, check format and auto-migrate if old:

if [ -f .planning/ROADMAP.md ]; then
  node scripts/kata-lib.cjs check-roadmap 2>/dev/null
  FORMAT_EXIT=$?

  if [ $FORMAT_EXIT -eq 1 ]; then
    echo "Old roadmap format detected. Running auto-migration..."
  fi
fi

If exit code 1 (old format):

Invoke kata-doctor in auto mode:

Skill("kata-doctor", "--auto")

Continue after migration completes.

If exit code 0 or 2: Continue silently.

cat .planning/STATE.md 2>/dev/null
cat .planning/ROADMAP.md 2>/dev/null

Parse current phase number from STATE.md "Current Position" section.

  1. Search for ### Phase {target}: heading
  2. If not found: ERROR: Phase {target} not found in roadmap Available phases: [list phase numbers] Exit.
  1. Compare target phase to current phase from STATE.md
  2. Target must be > current phase number

If target <= current phase:

ERROR: Cannot remove Phase {target}

Only future phases can be removed:
- Current phase: {current}
- Phase {target} is current or completed

To abandon current work, use /kata-pause-work instead.

Exit.

  1. Find and check for SUMMARY.md files in phase directory:
# Universal phase discovery for target phase
PADDED_TARGET=$(printf "%02d" "$TARGET" 2>/dev/null || echo "$TARGET")
PHASE_DIR=""
for state in active pending completed; do
  PHASE_DIR=$(find .planning/phases/${state} -maxdepth 1 -type d -name "${PADDED_TARGET}-*" 2>/dev/null | head -1)
  [ -z "$PHASE_DIR" ] && PHASE_DIR=$(find .planning/phases/${state} -maxdepth 1 -type d -name "${TARGET}-*" 2>/dev/null | head -1)
  [ -n "$PHASE_DIR" ] && break
done
# Fallback: flat directory (backward compatibility)
if [ -z "$PHASE_DIR" ]; then
  PHASE_DIR=$(find .planning/phases -maxdepth 1 -type d -name "${PADDED_TARGET}-*" 2>/dev/null | head -1)
  [ -z "$PHASE_DIR" ] && PHASE_DIR=$(find .planning/phases -maxdepth 1 -type d -name "${TARGET}-*" 2>/dev/null | head -1)
fi

find "${PHASE_DIR}" -maxdepth 1 -name "*-SUMMARY.md" 2>/dev/null

If any SUMMARY.md files exist:

ERROR: Phase {target} has completed work

Found executed plans:
- {list of SUMMARY.md files}

Cannot remove phases with completed work.

Exit.

  1. Extract phase name from ROADMAP.md heading: ### Phase {target}: {Name}
  2. Phase directory already found via universal discovery: ${PHASE_DIR}
  3. Find all subsequent phases (searching across active/pending/completed subdirectories) (integer and decimal) that need renumbering

Subsequent phase detection:

For integer phase removal (e.g., 17):

  • Find all phases > 17 (integers: 18, 19, 20...)
  • Find all decimal phases >= 17.0 and < 18.0 (17.1, 17.2...) → these become 16.x
  • Find all decimal phases for subsequent integers (18.1, 19.1...) → renumber with their parent

For decimal phase removal (e.g., 17.1):

  • Find all decimal phases > 17.1 and < 18 (17.2, 17.3...) → renumber down
  • Integer phases unchanged

List all phases that will be renumbered.

Removing Phase {target}: {Name}

This will:
- Delete: ${PHASE_DIR}
- Renumber {N} subsequent phases:
  - Phase 18 → Phase 17
  - Phase 18.1 → Phase 17.1
  - Phase 19 → Phase 18
  [etc.]

Proceed? (y/n)

Wait for confirmation.

if [ -d "${PHASE_DIR}" ]; then
  rm -rf "${PHASE_DIR}"
  echo "Deleted: ${PHASE_DIR}"
fi

If directory doesn't exist, note: "No directory to delete (phase not yet created)"

For each phase directory that needs renumbering (in reverse order to avoid conflicts):

Find each subsequent phase using universal discovery, then rename within the same state subdirectory:

# For each subsequent phase, find it across state subdirectories
for state in active pending completed; do
  # Example: renaming 18-dashboard to 17-dashboard within the same state dir
  SRC=$(find .planning/phases/${state} -maxdepth 1 -type d -name "18-dashboard" 2>/dev/null | head -1)
  [ -n "$SRC" ] && mv "$SRC" ".planning/phases/${state}/17-dashboard"
done
# Fallback: flat directory
SRC=$(find .planning/phases -maxdepth 1 -type d -name "18-dashboard" 2>/dev/null | head -1)
[ -n "$SRC" ] && mv "$SRC" ".planning/phases/17-dashboard"

Process in descending order (20→19, then 19→18, then 18→17) to avoid overwriting.

Also rename decimal phase directories:

  • 17.1-fix-bug → 16.1-fix-bug (if removing integer 17)
  • 17.2-hotfix → 17.1-hotfix (if removing decimal 17.1)

For each renumbered directory, rename files that contain the phase number:

# Inside 17-dashboard (was 18-dashboard):
mv "18-01-PLAN.md" "17-01-PLAN.md"
mv "18-02-PLAN.md" "17-02-PLAN.md"
mv "18-01-SUMMARY.md" "17-01-SUMMARY.md"  # if exists
# etc.

Also handle CONTEXT.md and DISCOVERY.md (these don't have phase prefixes, so no rename needed).

  1. Remove the phase section entirely:

- Delete from ### Phase {target}: to the next phase heading (or section end)

  1. Remove from phase list:

- Delete line - [] **Phase {target}: {Name}** or similar

  1. Remove from Progress table:

- Delete the row for Phase {target}

  1. Renumber all subsequent phases:

- ### Phase 18: → ### Phase 17: - - [] **Phase 18: → - [] **Phase 17: - Table rows: | 18. Dashboard | → | 17. Dashboard | - Plan references: 18-01: → 17-01:

  1. Update dependency references:

- **Depends on:** Phase 18 → **Depends on:** Phase 17 - For the phase that depended on the removed phase: - **Depends on:** Phase 17 (removed) → **Depends on:** Phase 16

  1. Renumber decimal phases:

- ### Phase 17.1: → ### Phase 16.1: (if integer 17 removed) - Update all references consistently

Write updated ROADMAP.md.

  1. Update total phase count:

- Phase: 16 of 20 → Phase: 16 of 19

  1. Recalculate progress percentage:

- New percentage based on completed plans / new total plans

Do NOT add a "Roadmap Evolution" note - the git commit is the record.

Write updated STATE.md.

# Find files that reference the old phase numbers (search across state subdirectories)
for state in active pending completed; do
  grep -r "Phase 18" .planning/phases/${state}/17-*/ 2>/dev/null
  grep -r "Phase 19" .planning/phases/${state}/18-*/ 2>/dev/null
done
# Fallback: flat directories
grep -r "Phase 18" .planning/phases/17-*/ 2>/dev/null
grep -r "Phase 19" .planning/phases/18-*/ 2>/dev/null
# etc.

Update any internal references to reflect new numbering.

Check planning config:

COMMIT_PLANNING_DOCS=$(node scripts/kata-lib.cjs read-config "commit_docs" "true")
git check-ignore -q .planning 2>/dev/null && COMMIT_PLANNING_DOCS=false

If COMMIT_PLANNING_DOCS=false: Skip git operations

If COMMIT_PLANNING_DOCS=true (default):

git add .planning/
git commit -m "chore: remove phase {target} ({original-phase-name})"

The commit message preserves the historical record of what was removed.

Phase {target} ({original-name}) removed.

Changes:
- Deleted: ${PHASE_DIR}
- Renumbered: Phases {first-renumbered}-{last-old} → {first-renumbered-1}-{last-new}
- Updated: ROADMAP.md, STATE.md
- Committed: chore: remove phase {target} ({original-name})

Current roadmap: {total-remaining} phases
Current position: Phase {current} of {new-total}

---

## What's Next

Would you like to:
- `/kata-track-progress` — see updated roadmap status
- Continue with current phase
- Review roadmap

---

<anti_patterns>

  • Don't remove completed phases (have SUMMARY.md files)
  • Don't remove current or past phases
  • Don't leave gaps in numbering - always renumber
  • Don't add "removed phase" notes to STATE.md - git commit is the record
  • Don't ask about each decimal phase - just renumber them
  • Don't modify completed phase directories </anti_patterns>

<edge_cases>

Removing a decimal phase (e.g., 17.1):

  • Only affects other decimals in same series (17.2 → 17.1, 17.3 → 17.2)
  • Integer phases unchanged
  • Simpler operation

No subsequent phases to renumber:

  • Removing the last phase (e.g., Phase 20 when that's the end)
  • Just delete and update ROADMAP.md, no renumbering needed

Phase directory doesn't exist:

  • Phase may be in ROADMAP.md but directory not created yet
  • Skip directory deletion, proceed with ROADMAP.md updates

Decimal phases under removed integer:

  • Removing Phase 17 when 17.1, 17.2 exist
  • 17.1 → 16.1, 17.2 → 16.2
  • They maintain their position in execution order (after current last integer)

</edge_cases>

<success_criteria> Phase removal is complete when:

  • Target phase validated as future/unstarted
  • Phase directory deleted (if existed)
  • All subsequent phase directories renumbered
  • Files inside directories renamed ({old}-01-PLAN.md → {new}-01-PLAN.md)
  • ROADMAP.md updated (section removed, all references renumbered)
  • STATE.md updated (phase count, progress percentage)
  • Dependency references updated in subsequent phases
  • Changes committed with descriptive message
  • No gaps in phase numbering
  • User informed of changes </success_criteria>

平台分布

Codex

39.11%
按下载量换算61

Claude

28.74%
按下载量换算45

Cursor

19.04%
按下载量换算30

Gemini CLI

9.04%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills