Merge pull request #349 from domaframework/document/add-claude-code-document

Add CLAUDE.md documentation for plugin development guidance

Author: xterao

.claude/commands/execute_issue.md

@@ -0,0 +1,11 @@
+gh issue view $ARGUMENTS to check the content of a GitHub Issue and proceed with the task.
+Follow the steps below to complete the task:
+
+1. Review the content of the Issue.
+2. Checkout and pull the latest state of the main branch.
+3. Create and checkout an appropriate branch based on the Issue content.
+4. Implement test code and test files that cover the cases described in the Issue. Refer to the [Test Case Implementation Guidelines](../guidelines/TEST_CASE_GUIDELINE) for rules on implementing test cases.
+5. Run the tests and ensure all tests pass.
+6. Create commits with appropriate granularity.
+7. Create a PR following the rules below:
+   - Refer to the [PR Creation Guidelines](../guidelines/CREATE_PR_GUIDELINE.md) for PR rules.

.claude/guidelines/CREATE_PR_GUIDELINE.md

@@ -0,0 +1,10 @@
+## Commit Guidelines
+- Use imperative mood for commit messages (e.g., "Fix bug" instead of "Fixed
+- Write Commit messages in English
+
+## PR Guidelines
+- If there are unstaged changes when creating a pull request, please split them appropriately and commit them separately.
+- Use the [PR Template](../templates/PR_TEMPLATE.md) for PR descriptions
+- PR titles should be concise and descriptive
+- Ensure all tests pass before submitting a PR
+- Write PR title and descriptions in English

.claude/guidelines/TEST_CASE_GUIDELINE.md

@@ -0,0 +1,30 @@
+# Test Case Implementation Guidelines
+Follow the rules below when implementing test code.
+
+## Code Inspection Functionality
+Implement tests for code inspection functionality using the following steps:
+
+### **Implementation of Test Case Classes**
+- Implement test case classes in `@src/test/kotlin/org/domaframework/doma/intellij/inspection`.
+- Implement test cases for each subclass of **AbstractBaseJavaLocalInspectionTool**.
+- Name the test case class as `<InspectionToolName>InspectionTest`.
+- The test case class should extend `DomaSqlTest`.
+- Override **setUp()** to add mock **Entity** classes or other necessary components to the virtual project for testing.
+- Register the target **AbstractBaseJavaLocalInspectionTool** subclass using **myFixture.enableInspections**.
+- In test case functions, retrieve the target Dao class using **DomaSqlTest#findDaoClass()** and test the highlighting results using **myFixture.testHighlighting()**.
+
+### Implementation of Test Cases
+Create the target Dao class or SQL file for inspection.
+Wrap the elements to be error-highlighted with the **<error>** tag and specify the error message to be displayed using the **descr** option.
+
+#### Test Data for Dao Classes
+- Implement test data Dao classes in **Java**.
+- Annotate test data Dao classes with **@Dao**.
+- Place them under the appropriate subpackage in `@src/test/testData/src/main/java/doma/example/dao/inspection`.
+- Implement any other necessary classes as needed.
+
+#### Test Data for SQL Files
+- Create and place SQL files in a directory named after the corresponding Dao class under `@src/test/testData/src/main/resources/META-INF/doma/example/dao`.
+
+### Reference
+For actual implementation examples using Doma, refer to the [Doma GitHub repository](https://github.com/domaframework/doma/tree/master/integration-test-java/src/main/java/org/seasar/doma/it/dao).