## Summary This PR integrates Claude Code AI assistant capabilities into the Nx repository through GitHub Actions and workspace configuration. ## Changes Made ### 🤖 GitHub Actions Integration - **Added `.github/workflows/claude.yml`**: GitHub Actions workflow that triggers Claude Code on: - Issue comments containing `@claude` - Pull request review comments containing `@claude` - Pull request reviews containing `@claude` - New issues with `@claude` in title or body - Configured appropriate permissions for repository access and PR/issue management - See [Claude Code GitHub Actions documentation](https://docs.anthropic.com/en/docs/claude-code/cli-usage#github-actions) for usage details ### 📝 Project Documentation & Configuration - **Added `CLAUDE.md`**: Comprehensive instructions for Claude Code including: - Repository-specific guidance and best practices - Essential commands for development workflow - Testing procedures (individual projects → affected projects → e2e tests) - GitHub issue resolution workflow - Pre-push validation requirements - **Added `.claude/settings.json`**: Claude Code permissions and environment configuration - **Added `.mcp.json`**: Model Context Protocol server configuration for Nx workspace integration ### 🔧 Workspace Setup - **Updated `package.json`**: Added `nx-mcp` dependency for enhanced workspace integration - **Updated `pnpm-lock.yaml`**: Lock file changes for new dependency - **Updated `.gitignore`**: Added Claude-specific ignore patterns - **Updated `CODEOWNERS`**: Assigned ownership of Claude-related files to @FrozenPandaz - **Updated `CONTRIBUTING.md`**: Enhanced contribution guidelines with technology stack information ## Benefits - Enables AI-assisted development and issue resolution through GitHub - Provides Claude with deep understanding of Nx workspace structure via MCP - Establishes clear development workflows and validation procedures - Maintains security through configured permissions and environment settings ## Usage After this PR is merged, team members and contributors can: 1. Comment `@claude` in issues or PRs to get AI assistance 2. Use Claude Code locally with enhanced Nx workspace understanding 3. Follow established workflows for testing and validation For more information, see the [Claude Code documentation](https://docs.anthropic.com/en/docs/claude-code). ## Test Plan - [x] Verify GitHub Actions workflow syntax is valid - [x] Confirm Claude Code configuration files are properly structured - [x] Validate new dependency integration - [x] Test workflow triggers on issue/PR interactions 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
48 lines
1.4 KiB
Markdown
48 lines
1.4 KiB
Markdown
# Commit Command
|
|
|
|
## Description
|
|
|
|
Create a git commit following Nx repository standards and validation requirements.
|
|
|
|
## Usage
|
|
|
|
```bash
|
|
/commit [message]
|
|
```
|
|
|
|
## What this command does:
|
|
|
|
1. **Pre-commit validation**: Runs the full validation suite (`pnpm nx prepush`) to ensure code quality
|
|
2. **Formatting**: Automatically formats changed files with Prettier
|
|
3. **Testing**: Runs tests on affected projects to validate changes
|
|
4. **Commit creation**: Creates a well-formed commit with proper message formatting (without co-author attribution)
|
|
5. **Status reporting**: Provides clear feedback on the commit process
|
|
|
|
## Workflow:
|
|
|
|
1. Format any modified files with Prettier
|
|
2. Run the prepush validation suite
|
|
3. If validation passes, stage relevant changes
|
|
4. Create commit with descriptive message
|
|
5. Provide summary of what was committed
|
|
|
|
## Commit Message Format:
|
|
|
|
- Use conventional commit format when appropriate
|
|
- Include scope (e.g., `feat(core):`, `fix(angular):`, `docs(nx):`)
|
|
- Keep first line under 72 characters
|
|
- Include detailed description if needed
|
|
|
|
## Examples:
|
|
|
|
- `/commit "feat(core): add new project graph visualization"`
|
|
- `/commit "fix(react): resolve build issues with webpack config"`
|
|
- `/commit "docs(nx): update getting started guide"`
|
|
|
|
## Validation Requirements:
|
|
|
|
- All tests must pass
|
|
- Code must be properly formatted
|
|
- No linting errors
|
|
- E2E tests for affected areas should pass
|