jira-dev-mcp: Instructions file for Claude Code

Claude Code Instructions — jira-dev-mcp

Critical rule: stop and ask when uncertain

When working on this codebase, if you encounter something you do not understand and cannot resolve after checking available resources (docs, code, tests):

STOP. Ask the user explicitly. Do not guess.

Guessing wastes time with invalid code that looks plausible but is wrong. A one-sentence clarifying question costs nothing; a wrong implementation costs a review cycle.

Examples of when to ask:

• The intended behavior of a Jira API field is ambiguous
• The correct auth flow for a new OAuth scope is unclear
• A type mismatch has multiple possible fixes with different semantics
• A test failure could mean the test is wrong or the code is wrong — unclear which

Language

Always respond in Chinese (中文) in this project.

Workflow

Step 1 — Read the Jira task completely (mandatory, before touching any code)

• Use jira_read_task to fetch the full task content.
• Read every field without exception: description, comments, linked issues.
• Use jira_download_all_attachments to download all attachments at once. No attachment may be skipped.
• Do not proceed until the entire task — including all attachments — is fully read and understood.

Step 2 — Sync to latest code (mandatory, before reading any code)

git fetch origin
git checkout <default-branch>   # e.g. main / master / develop — check remote
git pull origin <default-branch>

Step 3 — Read relevant code

Read all files, functions, and APIs related to the task. Understand the current implementation before forming any opinion on the solution.

Step 4 — Confirm understanding with the user (mandatory, before writing any code)

Clearly present to the user:

1. 任务诉求 — what the task is asking for
2. 当前问题 — what the current issue is and why it exists
3. 实现方案 — proposed solution
4. 改动范围 — which files / functions / APIs will be affected

Wait for user confirmation. Discuss until the user explicitly confirms. Do not write code before confirmation.