cli: Instructions file for Codex

AGENTS.md - AI Development Guidelines

This document defines the standards and constraints that AI assistants must follow when developing the rc project.

Language Requirements

Important: All content must be in English, except for conversations with AI assistants which may use Chinese:

• Code comments
• Commit messages
• PR titles and descriptions
• Documentation in code
• Error messages in code
• Log messages
• Variable and function names

First-Principles Reasoning

Use first-principles thinking. Do not assume the user always has a fully formed understanding of what they want or how to achieve it. Start from the underlying need and problem, and proceed carefully. If the motivation or goal is unclear, stop and discuss it with the user. If the goal is clear but the proposed path is not the shortest or most effective, say so and recommend a better approach.

Workflow

0. Branch Base Policy

1. For any code change task, always base work on the latest origin/main.
2. Before implementing code changes, run git fetch origin and ensure your working branch is created from or rebased onto origin/main.
3. Exception: if the task explicitly asks to fix or update a specific PR branch, continue on that PR branch instead of rebasing to origin/main unless explicitly requested.

1. Before Starting

1. Understand the task goals and acceptance criteria
2. Identify related modules and existing tests

2. Before Modifying

1. Check if the target file is a protected file
2. If it's a protected file, follow the Breaking Change process
3. Read related existing code to understand patterns and conventions

3. During Implementation

1. Write tests first (red)
2. Implement minimum code to pass tests (green)
3. Refactor and clean up code
4. Ensure all tests pass

4. After Completion

⚠️ Important: All checks must pass before each commit!

1. Run cargo fmt --all - Code formatting
2. Run cargo clippy --workspace -- -D warnings - Static analysis, must have zero warnings
3. Run cargo test --workspace - Unit tests, must all pass
4. Only create a git commit after all above checks pass
   • Commit message format: feat(phase-N): <description>
   • Example: feat(phase-1): implement alias commands and core infrastructure