Repository reference

Project root

5 files▾

Overview

Start with the product brief and repository contract.

1▾

README.md
project root

Build and packaging

Native build graph and Python packaging entry points.

2▾

Repository policy

Ignore rules and licensing metadata for the whole project.

2▾

Python wrapper

6 files▾

Entry points

Package marker and the Python CLI command surface.

2▾

Configuration

Default values and runtime settings for the Python wrapper.

2▾

Output

Terminal printing and report shaping for Python-facing flows.

2▾

Native commands

8 files▾

Entry point

Top-level native executable dispatch.

1▾

main.cpp
src

Check command

Interface and implementation for inspection-only checks.

2▾

Doctor command

Interface and implementation for diagnosis and repair flows.

2▾

Planned commands

Reserved files for build, setup, and validate behaviors.

3▾

Native core

16 files▾

Reporting and process

Core report types and subprocess execution primitives.

3▾

Platform and hardware detection

Host, driver, GPU, and CUDA environment discovery.

8▾

Repair and build helpers

Configuration, repo patching, and builder orchestration.

5▾

Kernels and UI

9 files▾

Elementwise kernel

Simple elementwise CUDA sample and shared declarations.

2▾

Memory benchmark

Memory transfer benchmarking kernels and declarations.

2▾

Reduction kernel

Reduction sample kernels and matching headers.

2▾

UI layer

Terminal placeholders and native report rendering.

3▾

Automation and tests

11 files▾

Automation

Bootstrap helpers and Docker environments for local reproduction.

3▾

C++ tests

Native coverage for CUDA environment, driver, and GPU probes.

3▾

Python tests

CLI, configuration, and report-output verification in Python.

3▾

Vendored placeholders

Reserved directories for future third-party dependencies.

2▾

Repo manifest scanner and patcher

Implementedv0.0.0

src/core/repo.cpp

This is the most automation-heavy file in the repo today. It walks the current project tree, finds supported manifest files, flags known compatibility issues like `-m32`, `Win32`, and `CUDA_32_BIT_DEVICE_CODE ON`, and can rewrite them into safer 64-bit defaults.

repo.hpp doctor.cpp main.cpp

Reference

Defines the patch rules that convert known 32-bit build settings into x64-safe settings.
Skips internal and vendor directories such as `.git`, `.dist`, `build`, `node_modules`, and `third_party`.
Scans `CMakeLists.txt`, `package.json`, `Makefile`, `.cmake`, and `.mk` files.

Behavior

Scanning

Reads manifest files line-by-line and records file, line, description, and snippet whenever a known bad pattern appears.

Patching

Runs string replacements for every rule, writes changed files back to disk, and rescans the repo to confirm whether issues remain.

Reporting

Produces `ok` when manifests are clean, `issue` when bad settings remain, and richer messages that describe how many problems or files were changed.

Caveats

The current patching strategy is text replacement, which makes it simple and effective for known patterns but also intentionally narrow. It is not a full semantic build-system editor.

Previous

include/core/repo.hpp

Next

include/commands/check.hpp

Related files

Core contract

include/core/repo.hpp

Declares the structures used to report repo-level compatibility issues and to apply automatic manifest fixes.

Command implementation

src/commands/doctor.cpp

Extends `check` with repo scanning, optional auto-configuration, auto-fix behavior, and next-step generation.

Native entrypoint

src/main.cpp

Owns native argument validation, text and JSON rendering, exit codes, and the interactive handoff from `doctor` to `doctor auto`.