Tree Sitter2Abnf
C 63 completed
Other
unknown / go · tiny
26
Files
2,397
LOC
0
Frameworks
4
Languages
Pipeline State
completedRun ID
#1546241Phase
doneProgress
0%Started
2026-04-16 23:53:48Finished
2026-04-16 23:53:48LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
26.74Framework unique
—Isolation
—Last stage change
2026-05-10 03:34:57Deduplication group #47297
Member of a group with 1,212 similar repo(s) — canonical #186444 view group →
Repobility · open methodology · https://repobility.com/research/
🧪 Code Distillation
Browse all specs →AI Prompt
Create a command-line tool, similar to how one would use `tree-sitter2abnf`, written in Go. This tool should convert between tree-sitter's `grammar.json` format and extended ABNF format (RFC 5234). It needs to handle both directions based on the input file extension (`.json` to ABNF, `.abnf` to JSON). The tool should also support flags for specifying an output file and displaying the version. Please ensure it correctly implements the direct mappings for constructs like `SEQ`, `CHOICE`, and `REPEAT`, as well as the rule-level annotations like `@field` and `@pattern`.
go cli parser grammar json abnf command-line tree-sitter
Generated by gemma4:latest
Catalog Information
Create a command-line tool, similar to how one would use tree-sitter2abnf, written in Go. This tool should convert between tree-sitter's grammar.json format and extended ABNF format (RFC 5234). It needs to handle both directions based on the input file extension (.json to ABNF, .abnf to JSON). The tool should also support flags for specifying an output file and displaying the version. Please ensure it correctly implements the direct mappings for constructs like SEQ, CHOICE, and `REPE
Tags
go cli parser grammar json abnf command-line tree-sitter
Quality Score
C
63.1/100
Structure
69
Code Quality
51
Documentation
59
Testing
50
Practices
74
Security
90
Dependencies
80
Strengths
- Good test coverage (80% test-to-source ratio)
- Consistent naming conventions (snake_case)
- Good security practices — no major issues detected
- Properly licensed project
Weaknesses
- No CI/CD configuration — manual testing and deployment
- Potential hardcoded secrets in 1 files
- 322 duplicate lines detected — consider DRY refactoring
- 1 'god files' with >500 LOC need decomposition
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
- Move hardcoded secrets to environment variables or a secrets manager
Languages
Frameworks
None detected
Symbols
method36
constant32
function22
struct8
type_alias1
Embed Badge
Add to your README:
