研究检索执行命令github未标认证来源可访问许可证需确认审计通过

ah-finalize-code（啊最终确定代码）

Agent Skill

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

总安装

212

周安装

GitHub Stars

公开资料未说明

下载量

CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill：ah-finalize-code（啊最终确定代码）
来源仓库：https://github.com/arinhubcom/arinhub
仓库路径：skills/ah-finalize-code
安装命令：
npx skills add https://github.com/arinhubcom/arinhub --skill ah-finalize-code
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

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

skills.shnpx skills

npx skills add https://github.com/arinhubcom/arinhub --skill ah-finalize-code

简介

orchestrate 代码最终化流程，包括简化、测试、文档化和审查的全套工作流。

适用于发布前的代码质量保障和版本冻结，确保符合规范后再提交 PR。
通过 npx 命令安装，默认使用 Opus 模型执行各子步骤并自动提交变更。
建议在非主干分支运行，并保留回滚能力以防意外修改。
ah-finalize-code 属于研究检索类 Skill，可作为该场景下的辅助能力补充。

SKILL.md

Finalize Code

Orchestrate the full pre-PR finalization workflow for the current branch. This involves running a sequence of specialized subagents -- each handling a different aspect of the finalization (simplification, testing, documentation, specs, code review) -- with a commit after every step. The workflow ends by creating a pull request.

Configuration

Subagent model defaults: Opus for all subagents except committer, which uses Sonnet
Thinking mode: ultrathink effort for all subagents

Procedure

0. Initialize

BRANCH_NAME=$(git branch --show-current)
REPO_NAME=$(basename -s .git "$(git remote get-url origin)")
SAFE_BRANCH_NAME=$(echo "${BRANCH_NAME}" | tr '/' '-')
SPEC_DIR="specs/${BRANCH_NAME}"
PROGRESS_FILE="~/.agents/arinhub/progresses/progress-pr-${REPO_NAME}-${SAFE_BRANCH_NAME}.md"

Read ${SPEC_DIR}/spec.md and extract:

BASE_BRANCH from the Base Branch metadata field
ISSUE_NUMBER from the Issue Number metadata field

If either value is missing from spec.md, ask the user before proceeding.

Compute the merge base for the current branch:

MERGE_BASE=$(git merge-base "${BASE_BRANCH}" HEAD)

Each subagent that analyzes code changes must compute its own fresh diff before starting its work:

DIFF=$(git diff "${MERGE_BASE}")

This ensures every subagent sees the latest state of changes, including modifications committed by previous steps.

If the repository is a monorepo, identify the correct application from the changed files in the diff and run all commands in the context of that application.

Read the template from references/progress-pr.md, replace all <BRANCH_NAME>, <BASE_BRANCH>, <ISSUE_NUMBER>, and <TIMESTAMP> placeholders with actual values, and write the result to ${PROGRESS_FILE}. Every subagent updates its own section after completing its work.