Claude Code configuration (#445)

Co-authored-by: Jeremy Mailen <[email protected]>

Author: jeremymailen

.claude/commands/fix-github-issue.md

@@ -0,0 +1,13 @@
+Please analyze and fix the GitHub issue: $ARGUMENTS.
+
+Follow these steps:
+
+1. Use `gh issue view` to get the issue details
+2. Understand the problem described in the issue
+3. Search the codebase for relevant files
+4. Implement the necessary changes to fix the issue
+5. Write and run tests to verify the fix
+6. Ensure code passes linting and type checking
+7. Create a descriptive commit message
+
+Remember to use the GitHub CLI (`gh`) for all GitHub-related tasks.

CLAUDE.md

@@ -0,0 +1,28 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Build and Test Commands
+
+- Build project: `./gradlew build`
+- Run all tests: `./gradlew test`
+- Run a single test: `./gradlew test --tests "org.jmailen.gradle.kotlinter.functional.KotlinProjectTest.testName"`
+- Run integration tests projects (from test-project* directories): `../gradlew lintKotlin formatKotlin`
+- Lint Kotlin code: `./gradlew lintKotlin`
+- Format Kotlin code: `./gradlew formatKotlin`
+- Lint specific source set: `./gradlew lintKotlinMain`
+- Format specific source set: `./gradlew formatKotlinMain`
+
+## Code Style Guidelines
+
+- Kotlin code follows ktlint rules with editorconfig customizations
+- Max line length: 140 characters
+- Indentation: 4 spaces
+- New line at EOF required
+- Trailing commas allowed in declarations and function calls
+- Imports follow ktlint standard ordering
+- Use kotlinter extension for configuration in Gradle projects
+- Tests use JUnit 5 (Jupiter) assertions
+- Functional tests extend `WithGradleTest` for Gradle TestKit integration
+- Error handling uses custom `KotlinterError` and `LintFailure` classes
+- When adding features, ensure backward compatibility as this is a Gradle plugin