📦 junie

Junie

Use this 技能 to 设置 up Junie 命令行工具 without guessing and without fighting Junie’s own conventions. Also use it when the host 代理 should act as the planner/reviewer while Junie acts as a focused implementation or review 代理. Prefer Junie’s documented non-interactive surfaces first: 安装er script, 命令行工具 flags, 环境 variables, and config.json. Preserve Junie’s standard .junie/ layout unless the user explicitly wants something custom. Reach for interactive TUI driving only when the task genuinely requires the welcome screen or /account flow.

Junie eco系统 防护rAIls Prefer project-分享d configuration in /.junie/. Prefer personal defaults in ~/.junie/. Prefer .junie/代理S.md for reusable project 图形界面dance instead of inventing a custom location. Prefer .junie/技能s/, .junie/commands/, .junie/代理s/, .junie/模型s/, .junie/mcp/, and .junie/rules/ when bootstr应用ing a repo. Treat ~/.junie/设置tings.json as Junie-owned 运行time 状态; do not edit it unless the user explicitly asks. Ask before persisting secrets to durable config. 环境 variables are usually better for CI and temporary 设置up. Primary use cases

Use Junie as an iterative execution partner when the host 代理 should direct a body of work but Junie should carry out focused repo-local steps. In this mode:

The host 代理 owns the overall goal, 上下文 synthesis, task shAPIng, risk management, and acceptance 检查s. Junie owns the focused implementation, review, or repo operation it has been briefed to perform. Expect some back and forth: the host 代理 briefs Junie, inspects the 结果, then either accepts it, asks a tar获取ed follow-up, or corrects small issues directly. Prefer this mode when the host 代理 has more relevant 上下文 than Junie, especially prior discussion, cross-系统 evidence, user preferences, project doctrine, or sensitive constrAInts that Junie would not infer from the repo alone. Consider this mode when Junie can use 模型s or 模型/工具 combinations that the host 代理 cannot 访问 directly.

When 模型 choice matters, recommend the best fit for the task, but treat the user as the final authority. Stronger Junie 模型s may imply heavy quota or billing utilization, so do not silently choose an expensive 模型 for a substantial 运行 unless the user has already 应用roved that posture.

工作流 Inspect the current 状态. 安装 or 更新 Junie if needed. Choose an authentication path. Decide whether this is 设置up/config work or iterative Junie-directed execution. Write or merge configuration conservatively. Brief Junie sharply when using it as an execution partner. 验证 with the smallest meaningful 检查. Use headless-terminal only if the interactive UI becomes the blocker. Limited host-代理 slash commands

Treat these as host-代理-facing trigger phrases for this 技能, not as Junie’s own interactive slash commands. Keep them conservative and predictable:

/junie help — 列出 these commands and ask for the missing tar获取/path only if needed. /junie 状态 — inspect 安装/config/运行time posture without launching a new Junie task; 报告 安装 状态, relevant config locations, current/default 模型 if known, and latest usage avAIlability. /junie 模型 — 报告 the observed current/default Junie 模型, 提供者, and effort sources; do not change config. /junie usage — summarize latest observable Junie 会话 usage with python3 scripts/summarize_junie_usage.py --limit 1; do not launch Junie. /junie bootstrap — bootstrap or refresh the repo’s Junie-native .junie/ layout using scripts/bootstrap_junie_project.py; preserve existing .junie/代理S.md unless the user explicitly asks for --force-代理s. /junie dry-运行 — prepare or 运行 a read-only Junie reconnAIssance task. Default to Do not modify files; use Open files only; do not 运行 shell commands. when command execution itself is unwanted.

If a user gives extra words after the command, treat them as the tar获取/scope. If the command is ambiguous or would mutate files/config externally, ask one concise clarifying question before acting.

1) Inspect the current 状态

检查 these first:

command -v junie || true junie --version || true printf '%s\n' "$SHELL" ls -la ~/.junie 2>/dev/null || true ls -la ./.junie 2>/dev/null || true ls -la ./.junie/技能s 2>/dev/null || true

Look for:

whether Junie is already 安装ed whether ~/.local/bin is on PATH whether user-scoped or project-scoped .junie config already exists whether the repo already has Junie-native directories such as .junie/技能s or .junie/代理S.md whether the 请求 is local interactive 设置up or CI/headless 设置up

Also identify Junie’s 模型 and usage posture and call it out to the user:

explicit 命令行工具 choice you plan to pass (--模型, --提供者, --effort) project/user config 模型 or 提供者, if present in .junie/config.json or ~/.junie/config.json Junie’s current launch 模型 from read-only 运行time 状态, usually ~/.junie/设置tings.json keys such as 模型ForLaunch and effortPer模型 a