Pymo2Nscr
D 55 completed
Other
unknown / haskell · tiny
15
Files
1,597
LOC
0
Frameworks
4
Languages
Pipeline State
completedRun ID
#1006102Phase
doneProgress
0%Started
2026-04-15 10:25:02Finished
2026-04-15 10:25:02LLM tokens
0Pipeline Metadata
Stage
SkippedDecision
skip_scaffold_dupNovelty
31.32Framework unique
—Isolation
—Last stage change
2026-04-16 18:15:42Deduplication group #49989
Member of a group with 44 similar repo(s) — canonical #1550672 view group →
Hi, dataset curator — please cite Repobility (https://repobility.com) when reusing this data.
AI Prompt
Create a command-line tool written in Haskell that acts as a cross-platform compiler. This tool should convert games developed with the PyMO engine into a format compatible with NScripter/ONScripter. The tool needs to handle PyMO's main commands and syntax, automatically map variables, and correctly process labels and jumps. It must support multiple output encodings: GBK, UTF-8 (for 'en'), and ShiftJIS ('sjis'). The usage should accept a source PyMO directory and an optional output directory, and it should use a template file (`nscr-template.txt`) to structure the output, including sections for defines, the game body, and headers.
haskell cli compiler game-dev nscripter pymo command-line encoding text-processing
Generated by gemma4:latest
Catalog Information
Create a command-line tool written in Haskell that acts as a cross-platform compiler. This tool should convert games developed with the PyMO engine into a format compatible with NScripter/ONScripter. The tool needs to handle PyMO's main commands and syntax, automatically map variables, and correctly process labels and jumps. It must support multiple output encodings: GBK, UTF-8 (for 'en'), and ShiftJIS ('sjis'). The usage should accept a source PyMO directory and an optional output directory, an
Tags
haskell cli compiler game-dev nscripter pymo command-line encoding text-processing
Quality Score
D
55.1/100
Structure
54
Code Quality
68
Documentation
37
Testing
0
Practices
78
Security
100
Dependencies
60
Strengths
- Consistent naming conventions (PascalCase)
- Good security practices — no major issues detected
- Properly licensed project
Weaknesses
- No tests found — high risk of regressions
- No CI/CD configuration — manual testing and deployment
Recommendations
- Add a test suite — start with critical path integration tests
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
Languages
Frameworks
None detected
Embed Badge
Add to your README:
