Imported from aiiware/aii-leetcode (AGENTS.md). Install upstream with npx skills add aiiware/aii-leetcode. Copyright stays with the author.

leetcode

Project Overview

This is a LeetCode solutions repository written in Go. The project organizes coding challenge solutions by algorithm and data structure categories (e.g., arrays, graphs, dynamic programming). It includes command-line entrypoints, utilities, documentation, and build scripts.

Directory Structure

cmd/ — Command entrypoints (Go)
docs/ — Documentation
scripts/ — Build and utility scripts
utils/ — Utility functions
advanced-algorithms/
arrays/
benchmarks/
data/
data_structures/
design/
dp/
explanations/
graphs/
indexes/
linked-lists/

File Patterns

• Source Files: Primarily use .go extension (552 files). A small number of .py files (15) are present.
• Test Files: Follow the Go convention *_test.go (e.g., handler_test.go).
• Naming: Files and directories predominantly use snake_case.
• Organization: Solutions are grouped into thematic directories like arrays/, graphs/, dp/, etc.

Core Commands

• Build: go build ./...
• Test: go test ./...

Git Conventions

• Convention: Conventional Commits.
• Default Branch: main.
• Common Commit Types & Scopes:
  • feat: (test, leetcode, design, graphs, benchmarks)
  • refactor: (organization, test, leetcode, tests, graph)
  • docs: (plan, agents, readme)
  • fix: (organization, reorganization, bit-manipulation, algorithm, binary)
  • test: (binary-tree, leetcode)
  • chore: (gitignore)

Example Commit Messages:

• feat(test): add comprehensive test suite for length of last word algorithm
• docs(plan): implement Phase 2 documentation system with templates and category overviews
• fix(organization): Fix build issues and update documentation
• refactor(organization): Refactor folder structure for better organization
• test(binary-tree): simplify test case tree representations

Coding Standards

• Language: Go.
• Linting/Testing: Uses the standard Go toolchain (go test, go build).
• File Naming: Adheres to Go conventions: lowercase, snake_case for multi-word names, with _test.go suffix for test files.
• Structure: Solution code is organized into packages by category (e.g., arrays/, dp/). The cmd/ directory contains application entry points.

Safety Rules

• Do NOT modify:
  • The go.mod and go.sum files without explicit approval.
  • Any existing AGENTS.md or other instruction files.
  • The LICENSE file.
  • CI/CD configuration files (if any are added in the future).
• Require confirmation for:
  • Any changes to the root-level directory structure (e.g., moving cmd/, utils/).
  • Modifying the scripts/ directory, as these may affect builds.
  • Deleting or significantly refactoring entire solution categories.

Permissions

• Allowed without prompt:
  • Adding new solution files within existing category directories (e.g., arrays/, graphs/).
  • Updating documentation in docs/.
  • Creating or updating Go test files (*_test.go).
  • Making minor refactors within a single file or package.
• Requires confirmation:
  • Creating new top-level directories.
  • Modifying files in cmd/ or utils/.
  • Running commands that affect dependencies (go get, go mod tidy).
  • Changing the project's AGENTS.md file.
• Never allowed:
  • Modifying go.mod or go.sum lock files.
  • Deleting the LICENSE file.
  • Changing the Git commit convention.

Generated by Aii CLI /init command with LLM enhancement (~961 tokens, 86 lines)