关于
This Claude Skill handles GitHub interactions specifically for the `Necmttn/ax` repository, allowing users to star it, file issues, or open pull requests via the `gh` CLI. It triggers only on explicit user requests for ax-related actions and always confirms before mutating account state. If the CLI is unavailable, it gracefully falls back to providing direct GitHub URLs.
快速安装
Claude Code
推荐npx skills add Necmttn/ax -a claude-code/plugin add https://github.com/Necmttn/axgit clone https://github.com/Necmttn/ax.git ~/.claude/skills/ax-repo在 Claude Code 中复制并粘贴此命令以安装该技能
技能文档
ax:repo
Let an AI coding agent interact with the ax GitHub repo (Necmttn/ax) for the
user - star, file an issue, or fork + open a PR - without the user
ever typing a gh command. Everything routes through the already-installed
gh CLI; there is no axctl surface for this.
Repo: Necmttn/ax · https://github.com/Necmttn/ax
When to fire
- "star ax" / "star the repo" / "I want to support ax" / "give ax a star"
- "report this as an ax bug" / "file an ax issue" / "open an issue on ax"
- "this looks like an ax bug" (after an
ax/axctlerror) - "I want to contribute to ax" / "fix this in ax" / "open a PR against ax"
Do NOT fire for GitHub work on other repos or for general gh usage.
Issues and PRs are user-initiated only. Star is the exception - you may
offer it proactively (see Proactive star nudge), but offering ≠ doing: the
actual star always needs an explicit yes.
Non-negotiable rules
- Preflight
ghfirst (read-only, no confirm). Detect three states:ghmissing → fall back to a plain URL (see Fallback). Don't error.ghpresent but unauthenticated → fall back to a plain URL, and tell the user they cangh auth loginto do it inline next time.ghpresent + authed → proceed to the action (still confirm mutations).
- Confirm before any account-mutating call - star, issue create, PR
create all change the user's GitHub account/repo. Show the exact command,
get an explicit yes. Read-only checks (
gh auth status, "is it starred") need NO confirm. - Never break the caller's exit code, never run silently in CI. If
$CIis set or stderr/stdin isn't a TTY, do NOT run mutatingghcalls - print the URL instead. A failedghcall must not abort the user's task.
Preflight (run this before every action)
if ! command -v gh >/dev/null 2>&1; then
echo "GH_STATE=missing"
elif ! gh auth status >/dev/null 2>&1; then
echo "GH_STATE=unauthed" # gh auth status exits 4 when not logged in
else
echo "GH_STATE=ok"
fi
missing/unauthed→ use Fallback for the chosen action.ok→ use theghcommand for the chosen action (after confirm).
Actions
1. Star
Mutates the user's account → confirm first.
# Optional read-only check (no confirm): is it already starred?
# exits 0 (starred) / non-zero / 404 (not starred)
gh api /user/starred/Necmttn/ax >/dev/null 2>&1 && echo "already starred"
# The star (after explicit yes):
gh api -X PUT /user/starred/Necmttn/ax # silent 204 on success
If already starred, say so and skip - don't re-PUT or re-prompt.
Unstar (only if asked): gh api -X DELETE /user/starred/Necmttn/ax.
You can also just run ax star, which stars via gh (or prints the URL) and
silences the CLI's periodic star reminder.
Fallback (gh missing/unauthed): print
https://github.com/Necmttn/ax and tell the user to click Star.
Proactive star prompting is NOT this skill's job - the CLI handles it deterministically (a once-a-day stderr footer shown only on an interactive terminal until the user runs
ax star/ax star --done). This skill only acts on an explicit user request.
2. File an issue / bug report
Mutates (creates an issue) → confirm first, and show the title/body you'll submit so the user can edit before you send it.
Interactive (opens a prefilled browser form - good default when the user wants to review/edit in GitHub's UI):
gh issue create --repo Necmttn/ax --web
Non-interactive (prefilled title + body, e.g. an error report you assembled):
gh issue create --repo Necmttn/ax \
--title "<concise summary>" \
--body "<body>" \
--label feedback # only if the user confirms; omit if unsure label exists
Error-report pattern. When firing off the back of an unhandled ax/axctl
error, prefill from the failure - never make the user paste a stack trace:
gh issue create --repo Necmttn/ax \
--title "ingest: <one-line error>" \
--body "$(cat <<'EOF'
**Command:** `ax <subcommand> <args>`
**ax version:** <output of `ax --version`>
**OS:** <uname -srm>
**What happened**
<one or two sentences>
**Error**
<the actual error output - trimmed, no secrets>
EOF
)"
Scrub paths/tokens that might leak private data before submitting. Confirm the assembled body with the user first.
Fallback (gh missing/unauthed): print the web new-issue URL. You can
prefill it via query string:
https://github.com/Necmttn/ax/issues/new?title=<urlencoded>&body=<urlencoded>
(plain https://github.com/Necmttn/ax/issues/new also works). Tell the user to
review and submit in the browser.
3. Fork + open a PR (contribute)
For a code change. Fork+clone is account-mutating → confirm before the fork and before the PR; branching/committing locally needs no confirm.
# 1. Fork and clone in one step (creates a fork on the user's account):
gh repo fork Necmttn/ax --clone # confirm: this creates a fork
# 2. From inside the clone, branch + make the change + commit:
git checkout -b <topic-branch>
# ...edits...
git commit -am "<conventional message>"
git push -u origin <topic-branch>
# 3. Open the PR against upstream (confirm before sending):
gh pr create --repo Necmttn/ax \
--title "<title>" --body "<what + why>"
# or interactively review in browser:
gh pr create --repo Necmttn/ax --web
If the user is already inside a clone of Necmttn/ax, skip the fork step;
gh pr create will offer to push to a fork automatically.
Fallback (gh missing/unauthed): print https://github.com/Necmttn/ax/fork
and tell the user to fork in the browser, then clone their fork manually.
House rules
- Show the exact
ghcommand before running any mutating one; get a yes. - One action per request - don't star and file an issue unless asked for both.
- Don't invent labels/milestones; omit
--labelif you're unsure it exists. - Keep issue bodies short, factual, secret-free; never paste raw transcripts.
- On any
ghfailure, surface the error and offer the URL fallback - never let it abort the user's in-progress task.
GitHub 仓库
常见问题
什么是 ax-repo Skill?
ax-repo 是一个 Claude Skill,作者为 Necmttn。Skill 将 Claude 按需加载的说明和资源打包,让 Claude 无需额外提示即可执行与 ax-repo 相关的任务。
如何安装 ax-repo?
使用本页的安装命令:将 ax-repo 作为插件添加到 Claude Code,或将其仓库克隆到 skills 目录,然后重启 Claude 以加载该 Skill。
ax-repo 属于哪个分类?
ax-repo 属于元分类。
ax-repo 可以免费使用吗?
可以。ax-repo 已收录在 AIMCP,可免费安装。
相关推荐技能
Content Collections 是一个 TypeScript 优先的构建工具,可将本地 Markdown/MDX 文件转换为类型安全的数据集合。它专为构建博客、文档站和内容密集型 Vite+React 应用而设计,提供基于 Zod 的自动模式验证。该工具涵盖从 Vite 插件配置、MDX 编译到生产环境部署的完整工作流。
这个Claude Skill为开发者提供完整的Polymarket预测市场开发支持,涵盖API调用、交易执行和市场数据分析。关键特性包括实时WebSocket数据流,可监控实时交易、订单和市场动态。开发者可用它构建预测市场应用、实施交易策略并集成实时市场预测功能。
该Skill帮助开发者创建OpenCode插件,用于接入命令、文件、LSP等25+种事件。它提供了插件结构、事件API规范和JavaScript/TypeScript实现模式,适合需要拦截操作、扩展功能或自定义事件处理的场景。开发者可通过它快速构建响应式模块来增强OpenCode AI助手的能力。
SGLang是一个专为LLM设计的高性能推理框架,特别适用于需要结构化输出的场景。它通过RadixAttention前缀缓存技术,在处理JSON、正则表达式、工具调用等具有重复前缀的复杂工作流时,能实现极速生成。如果你正在构建智能体或多轮对话系统,并追求远超vLLM的推理性能,SGLang是理想选择。
