Communitygithub.com

登陸報告 — 版本佇列儀表板

工作區感知的唯讀佇列儀表板(gstack)。

登陸報告 — 版本佇列儀表板 是什麼?

此技能提供一個唯讀的版本佇列儀表板,用於檢視目前有哪些 VERSION 插槽被開啟的 PR 佔用、哪些同級 Conductor 工作區有即將推出的 WIP 工作,以及 /ship 下一步會選取哪個插槽。它不會對系統進行任何修改,僅產生一個快照。此技能支援 Claude Code、Cursor、Codex 等平台,並透過 gstack 技能架構運作。觸發時會執行一個前置腳本,收集環境資訊(如分支名稱、工作階段類型、設定值);根據設定引導使用者完成功能探索(如設定重複檢查點、遙測與主動建議);並在第一次使用時提供專案特定的引導提示。執行期間會嚴格遵循計劃模式的行為規範,確保技能指令優先於通用計劃模式。

相容平台✓Claude Code✓Codex CLI~Cursor
npx skills add https://github.com/kelgirechandrakant-cpu/statsarthi/tree/HEAD/.agents/skills/landing-report

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

何時呼叫此技能

顯示哪些 VERSION 插槽 目前被開啟的 PR 佔用、哪些同級 Conductor 工作區有即將推出的 WIP 工作,以及 /ship 下一步會選取哪個插槽。不會有任何修改——僅是一個快照。當被問到「登陸報告」、「佇列中有什麼」、「顯示開啟的 PR」或「我下一步該認領哪個版本」時使用。

/landing-report — 版本佇列儀表板

前導(優先執行)

_UPD=$(~/.claude/skills/gstack/bin/gstack-update-check 2>/dev/null || .claude/skills/gstack/bin/gstack-update-check 2>/dev/null || true)
[ -n "$_UPD" ] && echo "$_UPD" || true
mkdir -p ~/.gstack/sessions
touch ~/.gstack/sessions/"$PPID"
_SESSIONS=$(find ~/.gstack/sessions -mmin -120 -type f 2>/dev/null | wc -l | tr -d ' ')
find ~/.gstack/sessions -mmin +120 -type f -exec rm {} + 2>/dev/null || true
_PROACTIVE=$(~/.claude/skills/gstack/bin/gstack-config get proactive 2>/dev/null || echo "true")
_PROACTIVE_PROMPTED=$([ -f ~/.gstack/.proactive-prompted ] && echo "yes" || echo "no")
_BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
echo "BRANCH: $_BRANCH"
_SKILL_PREFIX=$(~/.claude/skills/gstack/bin/gstack-config get skill_prefix 2>/dev/null || echo "false")
echo "PROACTIVE: $_PROACTIVE"
echo "PROACTIVE_PROMPTED: $_PROACTIVE_PROMPTED"
echo "SKILL_PREFIX: $_SKILL_PREFIX"
source <(~/.claude/skills/gstack/bin/gstack-repo-mode 2>/dev/null) || true
REPO_MODE=${REPO_MODE:-unknown}
echo "REPO_MODE: $REPO_MODE"
_SESSION_KIND=$(~/.claude/skills/gstack/bin/gstack-session-kind 2>/dev/null || echo "interactive")
case "$_SESSION_KIND" in spawned|headless|interactive) ;; *) _SESSION_KIND="interactive" ;; esac
echo "SESSION_KIND: $_SESSION_KIND"
# Conductor host: AskUserQuestion 在此處不可靠(原生已停用,MCP
# 變體不穩定),因此技能將決策以散文形式呈現,而不是呼叫工具。僅在非 headless 模式下執行,以便在 Conductor 內部(GSTACK_HEADLESS)的 eval/CI 執行仍然
# 封鎖,而不是對空無一人渲染散文。
if [ "$_SESSION_KIND" != "headless" ] && { [ -n "${CONDUCTOR_WORKSPACE_PATH:-}" ] || [ -n "${CONDUCTOR_PORT:-}" ]; }; then
  echo "CONDUCTOR_SESSION: true"
fi
_ACTIVATED=$([ -f ~/.gstack/.activated ] && echo "yes" || echo "no")
_FIRST_LOOP_SHOWN=$([ -f ~/.gstack/.first-loop-tip-shown ] && echo "yes" || echo "no")
echo "ACTIVATED: $_ACTIVATED"
echo "FIRST_LOOP_SHOWN: $_FIRST_LOOP_SHOWN"
# 首次執行專案偵測:僅在技能首次執行時執行偵測器
#(ACTIVATED=no,interactive),以便在後續每次執行時不影響熱路徑。
_FIRST_TASK=""
if [ "$_ACTIVATED" = "no" ] && [ "$_SESSION_KIND" != "headless" ]; then
  _FIRST_TASK=$(~/.claude/skills/gstack/bin/gstack-first-task-detect 2>/dev/null || true)
fi
echo "FIRST_TASK: $_FIRST_TASK"
_LAKE_SEEN=$([ -f ~/.gstack/.completeness-intro-seen ] && echo "yes" || echo "no")
echo "LAKE_INTRO: $_LAKE_SEEN"
_TEL=$(~/.claude/skills/gstack/bin/gstack-config get telemetry 2>/dev/null || true)
_TEL_PROMPTED=$([ -f ~/.gstack/.telemetry-prompted ] && echo "yes" || echo "no")
_TEL_START=$(date +%s)
_SESSION_ID="$$-$(date +%s)"
echo "TELEMETRY: ${_TEL:-off}"
echo "TEL_PROMPTED: $_TEL_PROMPTED"
_EXPLAIN_LEVEL=$(~/.claude/skills/gstack/bin/gstack-config get explain_level 2>/dev/null || echo "default")
if [ "$_EXPLAIN_LEVEL" != "default" ] && [ "$_EXPLAIN_LEVEL" != "terse" ]; then _EXPLAIN_LEVEL="default"; fi
echo "EXPLAIN_LEVEL: $_EXPLAIN_LEVEL"
_QUESTION_TUNING=$(~/.claude/skills/gstack/bin/gstack-config get question_tuning 2>/dev/null || echo "false")
echo "QUESTION_TUNING: $_QUESTION_TUNING"
_UPDATE_CHECK=$(~/.claude/skills/gstack/bin/gstack-config get update_check 2>/dev/null || echo "true")
echo "UPDATE_CHECK: $_UPDATE_CHECK"
mkdir -p ~/.gstack/analytics
if [ "$_TEL" != "off" ]; then
echo '{"skill":"landing-report","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","repo":"'$(_repo=$(basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null | tr -cd 'a-zA-Z0-9._-'); echo "${_repo:-unknown}")'"}'  >> ~/.gstack/analytics/skill-usage.jsonl 2>/dev/null || true
fi
for _PF in $(find ~/.gstack/analytics -maxdepth 1 -name '.pending-*' 2>/dev/null); do
  if [ -f "$_PF" ]; then
    if [ "$_TEL" != "off" ] && [ -x "$HOME/.claude/skills/gstack/bin/gstack-telemetry-log" ]; then
      ~/.claude/skills/gstack/bin/gstack-telemetry-log --event-type skill_run --skill _pending_finalize --outcome unknown --session-id "$_SESSION_ID" 2>/dev/null || true
    fi
    rm -f "$_PF" 2>/dev/null || true
  fi
  break
done
eval "$(~/.claude/skills/gstack/bin/gstack-slug 2>/dev/null)" 2>/dev/null || true
_LEARN_FILE="${GSTACK_HOME:-$HOME/.gstack}/projects/${SLUG:-unknown}/learnings.jsonl"
if [ -f "$_LEARN_FILE" ]; then
  _LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ')
  echo "LEARNINGS: $_LEARN_COUNT entries loaded"
  if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then
    ~/.claude/skills/gstack/bin/gstack-learnings-search --limit 3 2>/dev/null || true
  fi
else
  echo "LEARNINGS: 0"
fi
~/.claude/skills/gstack/bin/gstack-timeline-log '{"skill":"landing-report","event":"started","branch":"'"$_BRANCH"'","session":"'"$_SESSION_ID"'"}' 2>/dev/null &
_HAS_ROUTING="no"
for _RF in CLAUDE.md AGENTS.md; do
  if [ -f "$_RF" ] && grep -q "## Skill routing" "$_RF" 2>/dev/null; then
    _HAS_ROUTING="yes"
  fi
done
_ROUTING_DECLINED=$(~/.claude/skills/gstack/bin/gstack-config get routing_declined 2>/dev/null || echo "false")
echo "HAS_ROUTING: $_HAS_ROUTING"
echo "ROUTING_DECLINED: $_ROUTING_DECLINED"
_VENDORED="no"
if [ -d ".claude/skills/gstack" ] && [ ! -L ".claude/skills/gstack" ]; then
  if [ -f ".claude/skills/gstack/VERSION" ] || [ -d ".claude/skills/gstack/.git" ]; then
    _VENDORED="yes"
  fi
fi
echo "VENDORED_GSTACK: $_VENDORED"
echo "MODEL_OVERLAY: claude"
_CHECKPOINT_MODE=$(~/.claude/skills/gstack/bin/gstack-config get checkpoint_mode 2>/dev/null || echo "explicit")
_CHECKPOINT_PUSH=$(~/.claude/skills/gstack/bin/gstack-config get checkpoint_push 2>/dev/null || echo "false")
echo "CHECKPOINT_MODE: $_CHECKPOINT_MODE"
echo "CHECKPOINT_PUSH: $_CHECKPOINT_PUSH"
# Plan-mode hint for skills like /spec that branch behavior on plan-mode state.
# Claude Code exposes plan mode via system reminders; we detect best-effort
# from CLAUDE_PLAN_FILE (set by the harness when plan mode is active) and
# fall back to "inactive". Codex hosts and Claude execution mode both end up
# inactive, which is the safe default (defaults to file+execute pipeline).
if [ -n "${CLAUDE_PLAN_FILE:-}${GSTACK_PLAN_MODE_FORCE:-}" ]; then
  export GSTACK_PLAN_MODE="active"
elif [ "${GSTACK_PLAN_MODE:-}" = "active" ]; then
  export GSTACK_PLAN_MODE="active"
else
  export GSTACK_PLAN_MODE="inactive"
fi
echo "GSTACK_PLAN_MODE: $GSTACK_PLAN_MODE"
[ -n "$OPENCLAW_SESSION" ] && echo "SPAWNED_SESSION: true" || true

計劃模式安全操作

在計劃模式下,允許執行以下操作,因為它們有助於制定計劃:$B、$D、codex exec/codex review、寫入 ~/.gstack/、寫入計劃檔案,以及用於產出成果的 open。

計劃模式期間的技能呼叫

如果使用者在計劃模式下呼叫技能,則技能優先於通用計劃模式行為。將技能檔案視為可執行指令,而非參考資料。 從步驟 0 開始逐步執行;技能觸發的任何 AskUserQuestion 都是計劃模式內的工作流程操作,而非違反計劃模式——而一個其指令本身就能解決問題的技能(例如計劃模式自動選擇)可能合理地不會詢問。AskUserQuestion(任何變體——mcp__*__AskUserQuestion 或原生;請參閱「AskUserQuestion 格式 → 工具解析」)滿足計劃模式的回合結束要求。如果 AskUserQuestion 不可用或呼叫失敗,請遵循 AskUserQuestion 格式的失敗備援:headless → BLOCKED;interactive → 散文備援(也滿足回合結束)。在 STOP 點時,立即停止。請勿繼續工作流程或在該處呼叫 ExitPlanMode。標記為「PLAN MODE EXCEPTION — ALWAYS RUN」的命令會執行。僅在技能工作流程完成後,或使用者告訴您取消技能或離開計劃模式時,才呼叫 ExitPlanMode。

如果 PROACTIVE 為 "false",請勿自動呼叫或主動建議技能。如果某個技能看起來有幫助,請詢問:「I think /skillname might help here — want me to run it?」

如果 SKILL_PREFIX 為 "true",建議/呼叫 /gstack-* 名稱。磁碟路徑保持為 ~/.claude/skills/gstack/[skill-name]/SKILL.md。

如果 UPDATE_CHECK 為 "false",跳過接下來的兩行——更新檢查二進位檔在該模式下不會輸出任何內容,因此沒有 UPGRADE_AVAILABLE / JUST_UPGRADED 輸出需要處理。

如果輸出顯示 UPGRADE_AVAILABLE <old> <new>:讀取 ~/.claude/skills/gstack/gstack-upgrade/SKILL.md 並遵循「內聯升級流程」(如果已設定則自動升級,否則使用 4 個選項進行 AskUserQuestion,如果拒絕則寫入延遲狀態)。

如果輸出顯示 JUST_UPGRADED <from> <to>:列印「Running gstack v{to} (just updated!)」。如果 SPAWNED_SESSION 為 true,則跳過功能探索。

功能探索,每個會話最多一個提示:

  • 缺少 ~/.claude/skills/gstack/.feature-prompted-continuous-checkpoint:針對連續檢查點自動提交進行 AskUserQuestion。如果接受,執行 ~/.claude/skills/gstack/bin/gstack-config set checkpoint_mode continuous。一律觸碰標記。
  • 缺少 ~/.claude/skills/gstack/.feature-prompted-model-overlay:通知「Model overlays are active. MODEL_OVERLAY shows the patch.」一律觸碰標記。

升級提示後,繼續工作流程。

如果 WRITING_STYLE_PENDING 為 yes:詢問一次關於寫作風格:

v1 prompts are simpler: first-use jargon glosses, outcome-framed questions, shorter prose. Keep default or restore terse?

選項:

  • A) Keep the new default (recommended — good writing helps everyone)
  • B) Restore V0 prose — set explain_level: terse

如果選 A:保持 explain_level 未設定(預設為 default)。 如果選 B:執行 ~/.claude/skills/gstack/bin/gstack-config set explain_level terse。

始終執行(無論選擇為何):

rm -f ~/.gstack/.writing-style-prompt-pending
touch ~/.gstack/.writing-style-prompted

如果 WRITING_STYLE_PENDING 為 no,則跳過。

如果 LAKE_INTRO 為 no:說「gstack follows the Boil the Ocean principle — do the complete thing when AI makes marginal cost near-zero. Read more: https://garryslist.org/posts/boil-the-ocean」提供開啟連結:

open https://garryslist.org/posts/boil-the-ocean
touch ~/.gstack/.completeness-intro-seen

僅在回答為「是」時執行 open。始終執行 touch。

如果 TEL_PROMPTED 為 no 且 LAKE_INTRO 為 yes:透過 AskUserQuestion 詢問一次遙測:

Help gstack get better. Share usage data only: skill, duration, crashes, stable device ID. No code or file paths. Your repo name is recorded locally only and stripped before any upload.

選項:

  • A) Help gstack get better! (recommended)
  • B) No thanks

如果選 A:執行 ~/.claude/skills/gstack/bin/gstack-config set telemetry community

如果選 B:詢問後續問題:

Anonymous mode sends only aggregate usage, no unique ID.

選項:

  • A) Sure, anonymous is fine
  • B) No thanks, fully off

如果 B→A:執行 ~/.claude/skills/gstack/bin/gstack-config set telemetry anonymous 如果 B→B:執行 ~/.claude/skills/gstack/bin/gstack-config set telemetry off

始終執行:

touch ~/.gstack/.telemetry-prompted

如果 TEL_PROMPTED 為 yes,則跳過。

如果 PROACTIVE_PROMPTED 為 no 且 TEL_PROMPTED 為 yes:詢問一次:

Let gstack proactively suggest skills, like /qa for "does this work?" or /investigate for bugs?

選項:

  • A) Keep it on (recommended)
  • B) Turn it off — I'll type /commands myself

如果選 A:執行 ~/.claude/skills/gstack/bin/gstack-config set proactive true 如果選 B:執行 ~/.claude/skills/gstack/bin/gstack-config set proactive false

始終執行:

touch ~/.gstack/.proactive-prompted

如果 PROACTIVE_PROMPTED 為 yes,則跳過。

首次執行引導(一次性)

如果 ACTIVATED 為 no(此機器上首次執行技能)且前導腳本輸出一個非空的 FIRST_TASK: 值,且該值不是 nongit:顯示一個簡短的、專案特定的訊息(根據 token 映射),作為提示,然後繼續執行使用者實際要求的任務——不要中斷他們的任務。Token 映射:greenfield → 「Fresh repo — shape it first with /spec or /office-hours.」code_node/code_python/code_rust/code_go/code_ruby/code_ios → 「There's code here — /qa to see it work, or /investigate if something's off.」branch_ahead → 「Unshipped work on this branch — /review then /ship.」dirty_default → 「Uncommitted changes — /review before committing.」clean_default → 「Pick one: /spec, /investigate, or /qa.」然後將您看到的 token 代入 TASK_TOKEN 並執行(盡力而為),並標記為已啟用:

~/.claude/skills/gstack/bin/gstack-telemetry-log --event-type first_task_scaffold_shown --skill "TASK_TOKEN" --outcome shown 2>/dev/null || true
touch ~/.gstack/.activated 2>/dev/null || true

如果 ACTIVATED 為 no 但 FIRST_TASK: 為空或為 nongit(headless、非 git 或無可執行的操作):不顯示任何內容,僅執行 touch ~/.gstack/.activated 2>/dev/null || true。

否則,如果 ACTIVATED 為 yes 且 FIRST_LOOP_SHOWN 為 no:說一次作為提示(然後繼續):

Tip: gstack pays off when you complete one loop — plan → review → ship. A common first loop: /office-hours or /spec to shape it, /plan-eng-review to lock it, then /ship.

然後執行 touch ~/.gstack/.first-loop-tip-shown 2>/dev/null || true。

如果 ACTIVATED 和 FIRST_LOOP_SHOWN 都為 yes,則跳過此節。

如果 HAS_ROUTING 為 no 且 ROUTING_DECLINED 為 false 且 PROACTIVE_PROMPTED 為 yes: 檢查專案根目錄是否存在 CLAUDE.md 檔案。如果不存在,則建立它。

使用 AskUserQuestion:

gstack works best when your project's CLAUDE.md includes skill routing rules.

選項:

  • A) Add routing rules to CLAUDE.md (recommended)
  • B) No thanks, I'll invoke skills manua

...

[truncated for translation]

Individual skills in this repo

This repo contains 4 individual skills — each has its own dedicated page.

相關技能