Top 10 GitHub Project Setup Tricks You MUST Use in 2025!

npm install -g @anthropic-ai/claude-code

git clone https://github.com/vfarcic/dot-ai

cd dot-ai

git pull

devbox shell

export DOT_AI_IMAGE=ghcr.io/vfarcic/dot-ai:0.120.0

cat .github/ISSUE_TEMPLATE/config.yml

blank_issues_enabled: no
contact_links:
  - name: 💬 GitHub Discussions
    url: https://github.com/vfarcic/dot-ai/discussions
    about: Ask questions, share ideas, and discuss with the community
  - name: 📚 Documentation
    url: https://github.com/vfarcic/dot-ai#readme
    about: Read the documentation before reporting issues
  - name: ❓ Support Resources
    url: https://github.com/vfarcic/dot-ai/blob/main/SUPPORT.md
    about: Learn how to get help and where to ask questions
  - name: 🔒 Security Vulnerabilities
    url: https://github.com/vfarcic/dot-ai/blob/main/SECURITY.md
    about: Report security vulnerabilities privately following our security policy

cat .github/ISSUE_TEMPLATE/bug_report.yml

name: Bug Report
description: Report a bug to help us improve DevOps AI Toolkit
title: "[Bug]: "
labels: ["bug", "needs-triage"]
body:
  - type: markdown
    attributes:
      value: |
        Thank you for taking the time to report a bug! Please fill out the form below to help us diagnose and fix the issue.

        **Before submitting:**
        - Search existing issues to avoid duplicates
        - Check the [documentation](https://github.com/vfarcic/dot-ai#readme) for solutions
        - Review [SUPPORT.md](https://github.com/vfarcic/dot-ai/blob/main/SUPPORT.md) for help resources        

  - type: textarea
    id: description
    attributes:
      label: Bug Description
      description: A clear and concise description of what the bug is.
      placeholder: Describe the bug...
    validations:
      required: true

  - type: textarea
    id: steps-to-reproduce
    attributes:
      label: Steps to Reproduce
      description: Detailed steps to reproduce the behavior
      placeholder: |
        1. Go to '...'
        2. Run command '...'
        3. See error        
    validations:
      required: true

  - type: textarea
    id: expected-behavior
    attributes:
      label: Expected Behavior
      description: What you expected to happen
      placeholder: Describe what you expected...
    validations:
      required: true

  - type: textarea
    id: actual-behavior
    attributes:
      label: Actual Behavior
      description: What actually happened
      placeholder: Describe what actually happened...
    validations:
      required: true

  - type: markdown
    attributes:
      value: "## Environment"

  - type: input
    id: version
    attributes:
      label: "DevOps AI Toolkit Version"
      description: "What version are you running?"
      placeholder: "e.g., v1.2.3 or commit SHA"
    validations:
      required: true

  - type: input
    id: os
    attributes:
      label: Operating System
      description: "What OS are you using?"
      placeholder: "e.g., Ubuntu 22.04, macOS 13.5, Windows 11"
    validations:
      required: true

  - type: input
    id: node-version
    attributes:
      label: Node.js Version
      description: "Output of `node --version`"
      placeholder: "e.g., v18.17.0"
    validations:
      required: true

  - type: input
    id: npm-version
    attributes:
      label: npm/yarn Version
      description: "Output of `npm --version` or `yarn --version`"
      placeholder: "e.g., 9.6.7"

  - type: input
    id: kubernetes-version
    attributes:
      label: Kubernetes Version
      description: "Output of `kubectl version --short`"
      placeholder: "e.g., v1.27.3"
    validations:
      required: true

  - type: input
    id: cloud-provider
    attributes:
      label: Cloud Provider / Platform
      description: "Where is Kubernetes running?"
      placeholder: "e.g., AWS EKS, Google GKE, Azure AKS, self-hosted, minikube, kind"

  - type: textarea
    id: logs
    attributes:
      label: Relevant Logs
      description: "Paste any relevant log output here"
      placeholder: |
        Paste logs here...        
      render: shell
    validations:
      required: false

  - type: textarea
    id: additional-context
    attributes:
      label: Additional Context
      description: "Add any other context about the problem here (screenshots, configuration files, etc.)"
      placeholder: |
        Any additional information...        
    validations:
      required: false

  - type: checkboxes
    id: checklist
    attributes:
      label: Checklist
      options:
        - label: I have searched existing issues to ensure this bug hasn't been reported before
          required: true
        - label: I have included all relevant information above
          required: true

cat .github/ISSUE_TEMPLATE/feature_request.yml

name: Feature Request
description: Suggest a new feature or enhancement for DevOps AI Toolkit
title: "[Feature]: "
labels: ["enhancement", "needs-triage"]
body:
  - type: markdown
    attributes:
      value: |
        Thank you for suggesting a new feature! Please describe the problem you're trying to solve and your proposed solution.

        **Before submitting:**
        - Search existing issues and feature requests to avoid duplicates
        - Review the [project roadmap](https://github.com/vfarcic/dot-ai/blob/main/docs/ROADMAP.md) to see if this is already planned
        - Consider starting a [discussion](https://github.com/vfarcic/dot-ai/discussions) first to gather feedback

        **Note:** "Nice to have" is not a strong use case. Please explain the specific problem this feature would solve.        

  - type: textarea
    id: problem-statement
    attributes:
      label: Problem Statement
      description: What problem are you trying to solve? Why is it important?
      placeholder: |
        Describe the problem you're experiencing or the gap you've identified.
        Focus on the problem, not the solution.        
    validations:
      required: true

  - type: checkboxes
    id: who-is-affected
    attributes:
      label: Who is affected by this problem?
      description: Help us understand the impact and audience
      options:
        - label: End users
        - label: Developers/contributors
        - label: Platform engineers/operators
        - label: Documentation users
        - label: Other (please describe below)

  - type: textarea
    id: proposed-solution
    attributes:
      label: Proposed Solution
      description: Describe the solution you'd like to see
      placeholder: |
        How would this feature work? What would the user experience be?
        Be as specific as possible.        
    validations:
      required: true

  - type: textarea
    id: alternatives
    attributes:
      label: Alternatives Considered
      description: What other approaches have you considered or tried?
      placeholder: |
        - Current workarounds you're using
        - Other tools or features that solve similar problems
        - Why those alternatives don't fully address the need        
    validations:
      required: false

  - type: textarea
    id: use-cases
    attributes:
      label: Use Cases
      description: Describe 1-3 specific scenarios where this feature would be valuable
      placeholder: |
        **Use Case 1:** [Describe a specific scenario]
        **Use Case 2:** [Describe another scenario]        
      value: |
        **Use Case 1:**

        **Use Case 2:**        
    validations:
      required: true

  - type: textarea
    id: additional-context
    attributes:
      label: Additional Context
      description: Add any other context, screenshots, mockups, or examples
      placeholder: |
        - Links to relevant documentation
        - Screenshots or mockups
        - Examples from other projects
        - Performance or scalability considerations        
    validations:
      required: false

  - type: dropdown
    id: priority
    attributes:
      label: Priority
      description: How important is this feature to you?
      options:
        - "Nice to have"
        - "Important (workarounds exist but are painful)"
        - "Critical (blocking my use of DevOps AI Toolkit)"
    validations:
      required: true

  - type: dropdown
    id: contribution
    attributes:
      label: Are you willing to contribute this feature?
      description: Would you be interested in implementing this feature with guidance from maintainers?
      options:
        - "Yes, I'd like to implement this"
        - "Yes, with help from maintainers"
        - "Maybe, depending on complexity"
        - "No, but I can help test it"
        - "No, I'm just suggesting it"
    validations:
      required: false

  - type: checkboxes
    id: checklist
    attributes:
      label: Checklist
      options:
        - label: I have searched existing issues and feature requests
          required: true
        - label: I have described the problem, not just the solution
          required: true
        - label: I have reviewed the project roadmap (docs/ROADMAP.md)
          required: false

cat .github/PULL_REQUEST_TEMPLATE.md

<!--
Thank you for contributing to DevOps AI Toolkit! Please fill out this template to help us review your changes.
-->

## Description
<!-- Provide a clear and concise description of your changes -->

**What does this PR do?**

**Why is this change needed?**

## Related Issues
<!-- Link to related issues using keywords for automatic closure -->
<!-- Examples: "Closes #123", "Fixes #456", "Resolves #789" -->

- Related to: #

## Type of Change
<!-- Check all that apply -->

- [ ] 🐛 Bug fix (non-breaking change that fixes an issue)
- [ ] ✨ New feature (non-breaking change that adds functionality)
- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to change)
- [ ] 📚 Documentation update
- [ ] ♻️ Refactoring (no functional changes)
- [ ] ✅ Test updates (adding or updating tests)
- [ ] 🔧 Configuration changes
- [ ] 🚀 Performance improvements
- [ ] 🎨 Style changes (formatting, naming, etc.)
- [ ] 📦 Dependency updates
- [ ] 🔨 CI/CD changes

## Conventional Commit Format
<!-- This project uses Conventional Commits for automated changelog generation -->

**Your PR title should follow this format:**
    ```
    <type>(<scope>): <description>
    
    Examples:
      feat(auth): add OAuth2 authentication support
      fix(api): resolve null pointer exception in user service
      docs(readme): update installation instructions
      chore(deps): bump typescript from 5.0.0 to 5.1.0
    ```

**Common types:**
- `feat:` - New feature (minor version bump)
- `fix:` - Bug fix (patch version bump)
- `docs:` - Documentation changes
- `refactor:` - Code refactoring (no functional changes)
- `test:` - Adding/updating tests
- `chore:` - Maintenance tasks (dependencies, build, CI/CD)
- `perf:` - Performance improvements

**Breaking changes:**
    ```
    feat(api)!: remove deprecated v1 endpoints
    
    BREAKING CHANGE: v1 API endpoints have been removed.
    See MIGRATION.md for upgrade guide.
    ```

## Testing Checklist
<!-- Ensure all relevant tests have been completed -->

- [ ] Tests added or updated
- [ ] All existing tests pass locally
- [ ] Manual testing performed
- [ ] Test coverage maintained or improved

**Test commands run:**
    ```bash
    # Commands you ran locally to verify your changes
    # (Automated CI tests will run automatically on PR submission)
    ```

**Test results:**
<!-- Describe test results, including any relevant output or screenshots -->

## Documentation Checklist
<!-- Ensure documentation is updated to reflect your changes -->

- [ ] README.md updated (if user-facing changes)
- [ ] Documentation updated (if applicable)
- [ ] Code comments added for complex logic
- [ ] API documentation updated (if API changes)
- [ ] [CONTRIBUTING.md](CONTRIBUTING.md) guidelines followed

## Security Checklist
<!-- Complete if your changes affect security -->

- [ ] No secrets or credentials committed
- [ ] Input validation implemented where needed
- [ ] Security implications considered and documented
- [ ] Dependencies scanned for vulnerabilities
- [ ] Authentication/authorization logic reviewed
- [ ] Error messages don't leak sensitive information

## Breaking Changes
<!-- If this is a breaking change, describe the impact and provide migration guidance -->

**Does this PR introduce breaking changes?**
- [ ] Yes
- [ ] No

**If yes, describe the breaking changes and migration path:**

## Developer Certificate of Origin
<!-- This project requires DCO sign-off for all commits -->

By submitting this pull request, I certify that:

- The contribution was created in whole or in part by me and I have the right to submit it under the project's open source license.
- I understand and agree that this project and my contribution are public and that a record of the contribution (including all personal information I submit with it) is maintained indefinitely.

**DCO Sign-off:**
All commits must include a `Signed-off-by` line:
    ```bash
    git commit -s -m "Your commit message"
    ```

If you forgot to sign off your commits, you can amend them:
    ```bash
    git commit --amend --signoff
    git push --force-with-lease
    ```

## Checklist
<!-- Final pre-submission checklist -->

- [ ] My code follows the project's code style guidelines
- [ ] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] My changes generate no new warnings or errors
- [ ] I have added tests that prove my fix is effective or my feature works
- [ ] New and existing tests pass locally with my changes
- [ ] Any dependent changes have been merged and published
- [ ] All commits are signed off (DCO)
- [ ] PR title follows Conventional Commits format

## Additional Context
<!-- Add any other context, considerations, or notes for reviewers -->

**Reviewer Notes:**
<!-- Anything specific you want reviewers to focus on? -->

**Follow-up Work:**
<!-- Any planned follow-up PRs or related work? -->

claude --mcp-config .mcp-docker.json

/prd-done

...

  📋 Proposed PR Information (based on analysis)

  PR Title:
  fix(security): improve OpenSSF Scorecard score from 6.1 to 9.1

  Type of Change:
  - 🔧 Configuration changes
  - 📦 Dependency updates
  - 🔨 CI/CD changes

  Description:

  What does this PR do?
  Implements comprehensive OpenSSF Scorecard security improvements across GitHub
  Actions workflows, dependency management, and branch protection policies. Fixes 6
   critical and warning-level security checks to improve the project's security
  posture from 6.1/10 to an estimated 9.1/10.

  Why is this change needed?
  The project's OpenSSF Scorecard score of 6.1/10 indicated moderate security
  concerns that could reduce user trust, increase security risks, and limit
  adoption by security-conscious organizations. This PR addresses all high-priority
   security gaps identified in the scorecard analysis.

  Changes Made:
  - Token Permissions (0→10): Set minimal read-only permissions in all GitHub
  Actions workflows
  - Pinned Dependencies (3→10): Pinned all 13 GitHub Actions to commit SHA, Docker
  images to digest
  - SAST Analysis (7→10): Extended CodeQL security scanning to run on both PRs and
  main branch
  - Branch Protection (0→10): Enabled branch protection rules requiring PR reviews
  and status checks
  - Code Review (0→10): Enforced required reviews via branch protection
  - CI Tests (2→10): Branch protection ensures CI passes before merge
  - Repository Settings: Enforced squash merge for clean commit history

  Related Issues: Closes #184

  Manual Testing:
  - Verified GitHub Actions workflows execute with restricted permissions
  - Confirmed pinned Actions and Docker images resolve correctly
  - Validated CodeQL SAST analysis runs on both PR and main branch pushes
  - Tested branch protection prevents direct pushes and requires reviews
  - Confirmed renovate.json configuration enables automated dependency updates

  Breaking Changes: No

  Performance Impact: No performance impact - configuration and security
  improvements only

  Security Considerations:
  - Significantly improves project security posture
  - Reduces attack surface through minimal permissions
  - Prevents dependency confusion attacks via pinned versions
  - Enables continuous security monitoring via SAST

  Reviewer Focus:
  - Verify GitHub Actions workflows maintain functionality with restricted
  permissions
  - Confirm pinned dependency versions are correct and up-to-date
  - Validate branch protection rules don't overly restrict workflow
  - Check that SAST analysis configuration is appropriate

  Follow-up Work:
  - Monitor OpenSSF Scorecard for actual score validation (requires ~24 hours after
   merge)
  - Consider additional improvements documented in PRD Milestones 5-6 (deferred)
  - Maintain security posture through renovate-automated dependency updates

  Additional Context:
  This PR implements PRD #184 recommendations based on detailed OpenSSF Scorecard
  analysis. The estimated score improvement from 6.1 to 9.1 exceeds the original
  7.5 target. All changes are non-breaking and focus on hardening security without
  impacting development velocity.

  Appropriate Labels (from release.yml):
  Based on the changes, I recommend the label: fix (Bug Fixes category, since this
  fixes security issues)

  ---
  Please review and respond:
  - Type "yes" or "confirm" to accept all proposed information
  - Specify corrections for any items that need changes

Yes

cat .github/CODEOWNERS

# CODEOWNERS
#
# Code owners are automatically requested for review when someone opens a pull request
# that modifies code that they own. Code owners are not automatically requested to review
# draft pull requests.
#
# See: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

# Global owners (default for everything in the repository)
# Using individual maintainers for code ownership
* @vfarcic

# Notes:
# - Code owners are automatically requested for review when PRs modify their files
# - You can define path-specific owners by adding lines like:
#   /docs/ @docs-team
#   /.github/ @devops-team
#   /src/core/ @architecture-team
# - Order matters: later matches take precedence over earlier ones
# - Use teams (@org/team) for easier maintenance in larger projects

cat .github/release.yml

# Release notes configuration
#
# Configures automatic release notes generation when creating GitHub Releases.
# GitHub will categorize merged PRs based on labels and generate formatted changelog.
#
# See: https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes

changelog:
  exclude:
    labels:
      - skip-changelog
      - duplicate
      - invalid
      - wontfix
    authors:
      - renovate
      - renovate[bot]
      - github-actions[bot]

  categories:
    - title: Breaking Changes
      labels:
        - breaking-change
        - breaking

    - title: New Features
      labels:
        - feature
        - enhancement
        - feat

    - title: Bug Fixes
      labels:
        - bug
        - fix
        - bugfix

    - title: Documentation
      labels:
        - documentation
        - docs

    - title: Dependencies
      labels:
        - dependencies
        - deps
        - dependency

    - title: Other Changes
      labels:
        - "*"

cat .github/workflows/scorecard.yml

# This workflow uses actions that are not certified by GitHub. They are provided by a
# third-party and are governed by separate terms of service, privacy policy, and support
# documentation.
#
# OpenSSF Scorecard is a tool that assesses open source projects for security risks.
# Projects are given a score out of 10 based on security best practices.
# See: https://github.com/ossf/scorecard

name: OpenSSF Scorecard

on:
  # Only the default branch is supported for accurate security analysis
  push:
    branches:
      - main

  # Run security analysis on a schedule
  schedule:
    # 30 1 * * 6 - Weekly on Saturdays at 1:30 AM UTC
    - cron: '30 1 * * 6'

  # Allow manual triggering for on-demand security analysis
  workflow_dispatch:

# Restrict permissions to read-only by default for security
permissions: read-all

jobs:
  analysis:
    name: Scorecard analysis
    runs-on: ubuntu-latest
    permissions:
      # Required to upload results to GitHub's code scanning dashboard
      security-events: write
      # Required to publish results and get a Scorecard badge
      id-token: write
      # Required for private repos to detect SAST tools and query commits
      contents: read

    steps:
      - name: "Checkout code"
        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
        with:
          persist-credentials: false

      - name: "Run analysis"
        uses: ossf/scorecard-action@4eaacf0543bb3f2c246792bd56e8cdeffafb205a # v2.4.3
        with:
          results_file: results.sarif
          results_format: sarif
          # Publish results to enable Scorecard badges and REST API access
          # See: https://github.com/ossf/scorecard-action#publishing-results
          publish_results: true

      - name: "Upload artifact"
        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
        with:
          name: SARIF file
          path: results.sarif
          retention-days: 5

      - name: "Upload to code-scanning"
        uses: github/codeql-action/upload-sarif@64d10c13136e1c5bce3e5fbde8d4906eeaafc885 # v3.30.6
        with:
          sarif_file: results.sarif

cat renovate.json

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "config:base",
    ":dependencyDashboard",
    ":semanticCommits",
    ":separatePatchReleases"
  ],
  "schedule": ["before 9am on monday"],
  "timezone": "UTC",
  "labels": ["dependencies"],
  "assignees": ["@vfarcic"],
  "packageRules": [
    {
      "matchDepTypes": ["devDependencies"],
      "matchUpdateTypes": ["patch", "minor"],
      "automerge": true,
      "automergeType": "pr"
    },
    {
      "matchPackageNames": ["@types/*"],
      "matchUpdateTypes": ["patch", "minor"],
      "automerge": true,
      "groupName": "TypeScript definitions"
    },
    {
      "matchPackageNames": ["jest", "@types/jest", "ts-jest"],
      "groupName": "Jest packages"
    },
    {
      "matchPackageNames": ["eslint*", "prettier", "@typescript-eslint/*"],
      "groupName": "Linting tools"
    },
    {
      "matchPackageNames": ["@kubernetes/client-node"],
      "reviewersFromCodeOwners": true,
      "labels": ["kubernetes", "major-update"]
    },
    {
      "matchFiles": ["devbox.json"],
      "groupName": "Devbox packages",
      "labels": ["devbox"]
    }
  ],
  "vulnerabilityAlerts": {
    "enabled": true,
    "schedule": ["at any time"]
  },
  "lockFileMaintenance": {
    "enabled": true,
    "schedule": ["before 9am on monday"]
  },
  "prHourlyLimit": 3,
  "prConcurrentLimit": 5,
  "rebaseWhen": "conflicted",
  "commitMessageSuffix": " [skip ci]"
}

cat .github/labeler.yml

# This configuration automatically labels pull requests based on file paths.
# Learn more: https://github.com/actions/labeler

# Documentation changes
documentation:
- changed-files:
  - any-glob-to-any-file:
    - 'docs/**/*'
    - '*.md'
    - 'README*'

# Source code changes
source:
- changed-files:
  - any-glob-to-any-file:
    - 'src/**/*'

# Test changes
tests:
- changed-files:
  - any-glob-to-any-file:
    - 'tests/**/*'
    - '**/*.test.*'
    - '**/*.spec.*'

# CI/CD changes
ci-cd:
- changed-files:
  - any-glob-to-any-file:
    - '.github/workflows/**/*'
    - '.github/actions/**/*'
    - 'Dockerfile*'
    - 'docker-compose*.yml'

# Infrastructure changes
infrastructure:
- changed-files:
  - any-glob-to-any-file:
    - 'k8s/**/*'
    - 'kubernetes/**/*'
    - 'manifests/**/*'
    - 'helm/**/*'
    - 'charts/**/*'
    - 'Chart.yaml'
    - 'values.yaml'
    - 'kind.yaml'

# Dependencies
dependencies:
- changed-files:
  - any-glob-to-any-file:
    - 'package.json'
    - 'package-lock.json'
    - 'yarn.lock'
    - 'pnpm-lock.yaml'

# Configuration changes
config:
- changed-files:
  - any-glob-to-any-file:
    - '*.config.*'
    - '*.json'
    - '*.yaml'
    - '*.yml'
    - '*.toml'
    - '.env*'
    - 'tsconfig.json'
    - '.eslintrc*'
    - '.prettierrc*'

cat .github/workflows/labeler.yml

# This workflow automatically labels pull requests based on file paths.
# Configuration: .github/labeler.yml
# Learn more: https://github.com/actions/labeler

name: "Pull Request Labeler"

on:
- pull_request_target

permissions:
  contents: read
  pull-requests: write

jobs:
  labeler:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/labeler@v5
        with:
          configuration-path: .github/labeler.yml
          sync-labels: true

cat .github/workflows/stale.yml

# This workflow warns and then closes issues and PRs that have had no activity for a specified amount of time.
#
# Best practice: Only mark items stale when responsibility is on the contributor/user, not on maintainers.
# Items with labels indicating maintainer action needed should be exempt from stale automation.
#
# Learn more: https://github.com/actions/stale

name: Close Stale Issues and PRs

on:
  schedule:
    - cron: '0 0 * * *'
  workflow_dispatch:

permissions:
  issues: write
  pull-requests: write

jobs:
  stale:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/stale@5bef64f19d7facfb25b37b414482c7164d639639 # v9
        with:
          # Issues configuration
          days-before-issue-stale: 60
          days-before-issue-close: 7
          stale-issue-message: >
            This issue has been automatically marked as stale because it has not had
            recent activity. It will be closed if no further activity occurs. Thank you
            for your contributions.            
          close-issue-message: >
            This issue was automatically closed due to inactivity.
            If you believe this is still relevant, please reopen it.            
          stale-issue-label: 'stale'

          # Pull requests configuration
          days-before-pr-stale: 30
          days-before-pr-close: 7
          stale-pr-message: >
            This pull request has been automatically marked as stale because it has not had
            recent activity. It will be closed if no further activity occurs. Thank you
            for your contributions.            
          close-pr-message: >
            This pull request was automatically closed due to inactivity.
            If you believe this is still relevant, please reopen it.            
          stale-pr-label: 'stale'

          # Exemptions - Never mark these as stale (maintainer responsibility)
          exempt-issue-labels: 'pinned,security'
          exempt-pr-labels: 'pinned,security'
          exempt-milestones: true
          exempt-assignees: true

          # Behavior
          remove-stale-when-updated: true
          operations-per-run: 100

claude --mcp-config .mcp-docker.json

Setup project

⏺ Great! The repository analysis shows that most project files are already in place. Here's what I found:

  Repository Status

  Complete Scopes (✓):
  - ✓ readme: README.md exists
  - ✓ legal: LICENSE exists
  - ✓ governance: All 6 governance files exist (MAINTAINERS.md, GOVERNANCE.md, ROADMAP.md, SUPPORT.md, CODE_OF_CONDUCT.md, CONTRIBUTING.md)
  - ✓ github-issues: All 3 issue template files exist
  - ✓ pr-template: Pull request template exists
  - ✓ github-community: Community files exist
  - ✓ github-security: Security workflow exists
  - ✓ github-automation: All 4 automation workflows exist

  Incomplete Scopes (○):
  - ○ community: Missing ADOPTERS.md file

  Would you like me to generate the missing ADOPTERS.md file to complete the project setup?

git switch main

exit