gitflow-cli: Instructions file for Claude Code

gf Agent Guide

This repository is a reusable Rust 2024 workspace template. These rules are mandatory when working in this template.

Non-negotiables

• Never enter plan mode automatically.
• Preserve template placeholders such as gf unless the user explicitly asks to instantiate the template.
• Do not replace template variables with concrete project names during maintenance.
• Use CLAUDE.md as the single project-level agent instruction file.
• Use Ruflo for agent workflow/orchestration. Do not maintain project-local .claude/skills unless explicitly requested.
• Keep Ruflo or Claude-flow runtime state out of git; persist reusable guidance in CLAUDE.md, docs/, or specs/.
• Do not push, release, deploy, install dependencies, or change ticket state without explicit user permission.
• After merging a temporary issue branch, check that its worktree has no uncommitted changes, remove that worktree, and delete the merged local branch with git branch -d in the same task. Keep dev and main.
• Never run cargo clean; ask first if it is truly required.
• Never write TODO, todo!(), temporary stubs, or incomplete code. If blocked, stop, reassess, and implement the complete solution.
• Remove dead code instead of suppressing it. Do not add deprecation layers unless explicitly requested.
• Never expose secrets in commands, logs, URLs, comments, errors, or tool arguments.
• 禁止修改以下配置文件（除非用户明确要求）：deny.toml 中的 allow/deny/wildcards 等策略配置、.pre-commit-config.yaml 中的 hook 类型和阶段配置、rust-toolchain.toml 中的工具链版本。这些配置影响 CI/CD 流程，变更需用户确认。
• 严格执行 gf-workflow 流程：当使用 /gf-workflow 时，必须按照四阶段完整流程执行：
  • 阶段 1：需求澄清（从 open issues 读取，支持完整模式和快速模式）
  • 阶段 2：计划制定（生成完整计划闭环）
  • 阶段 3：执行（调用 subagent-driven-development）
  • 阶段 4：交付后检查（流水线分析、Issue 分类、代码审查）
  • 不可跳过: TDD 循环和代码审查在所有模式下均为必须步骤

Completion Discipline

• Do Not Stop Early: If the user's requested outcome is not fully complete, do not stop at a draft, partial pass, or "good enough" result. Continue reviewing and improving until the request is genuinely handled or a concrete blocker requires user input.
• Polish Bar: Before declaring work complete, ask whether the result is fully polished, concrete, correct, complete, and elegant. If there is doubt, review the work again and update it.
• Honest Status: Do not claim a task is finished when it is only a first pass, scaffold, or partial draft. State the remaining gaps and keep working unless the user explicitly asks to pause.