Agentic Chessengine Rocq Cc
C 60 completed
Other
unknown / vlang · tiny
20
Files
1,814
LOC
0
Frameworks
3
Languages
Pipeline State
completedRun ID
#1098810Phase
doneProgress
0%Started
2026-04-15 14:04:38Finished
2026-04-15 14:04:38LLM tokens
0Pipeline Metadata
Stage
SkippedDecision
skip_scaffold_dupNovelty
19.38Framework unique
—Isolation
—Last stage change
2026-04-16 18:15:42Deduplication group #47631
Member of a group with 18 similar repo(s) — canonical #1576798 view group →
Repobility · code-quality intelligence platform · https://repobility.com
AI Prompt
Create a chess engine that is written entirely in Rocq and extracted to OCaml, playable via the UCI protocol. The engine needs to handle move generation, evaluation, and search. Specifically, implement Negamax alpha-beta search with quiescence search and delta pruning. The evaluation function should incorporate material counting (Pawn=100, Knight=320, Bishop=330, Rook=500, Queen=900), piece-square tables, and a bishop pair bonus. The architecture should be modular, covering types, bitboard representation (using a two-word system for 64 squares), move generation, and the top-level entry point.
vlang ocaml chess engine rocq uci search bitboard game-ai
Generated by gemma4:latest
Catalog Information
Create a chess engine that is written entirely in Rocq and extracted to OCaml, playable via the UCI protocol. The engine needs to handle move generation, evaluation, and search. Specifically, implement Negamax alpha-beta search with quiescence search and delta pruning. The evaluation function should incorporate material counting (Pawn=100, Knight=320, Bishop=330, Rook=500, Queen=900), piece-square tables, and a bishop pair bonus. The architecture should be modular, covering types, bitboard repre
Tags
vlang ocaml chess engine rocq uci search bitboard game-ai
Quality Score
C
60.5/100
Structure
54
Code Quality
68
Documentation
34
Testing
40
Practices
78
Security
100
Dependencies
50
Strengths
- Good security practices — no major issues detected
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- No CI/CD configuration — manual testing and deployment
- 115 duplicate lines detected — consider DRY refactoring
Recommendations
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
Languages
Frameworks
None detected
Embed Badge
Add to your README:
