Rebar3 Kura

C 70 completed
Other
unknown / erlang · tiny
17
Files
1,979
LOC
0
Frameworks
3
Languages

Pipeline State

completed
Run ID
#1043329
Phase
done
Progress
0%
Started
2026-04-15 11:48:17
Finished
2026-04-15 11:48:17
LLM tokens
0

Pipeline Metadata

Stage
Cataloged
Decision
proceed
Novelty
41.93
Framework unique
Isolation
Last stage change
2026-05-10 03:34:29
Deduplication group #55590
Member of a group with 16 similar repo(s) — canonical #1104845 view group →
Repobility — same analyzer, your code, free for public repos · /scan/

AI Prompt

Create a Rebar3 plugin for Kura that automates database migration file generation based on schema changes. I need it to run as a pre-compile hook, automatically detecting new tables, added columns, dropped columns, and type changes by comparing the `kura_schema` modules against existing migrations. The tool should also provide a command to bootstrap a new Kura project, which generates a repository module and the necessary `src/migrations/` directory structure. Please ensure the documentation explains which changes, like `drop_table` or primary key changes, it explicitly skips generating.
erlang rebar3 kura database migration plugin schema build-tool
Generated by gemma4:latest

Catalog Information

Create a Rebar3 plugin for Kura that automates database migration file generation based on schema changes. I need it to run as a pre-compile hook, automatically detecting new tables, added columns, dropped columns, and type changes by comparing the kura_schema modules against existing migrations. The tool should also provide a command to bootstrap a new Kura project, which generates a repository module and the necessary src/migrations/ directory structure. Please ensure the documentation exp

Tags

erlang rebar3 kura database migration plugin schema build-tool

Quality Score

C
69.5/100
Structure
83
Code Quality
50
Documentation
39
Testing
85
Practices
78
Security
100
Dependencies
50

Strengths

  • CI/CD pipeline configured (github_actions)
  • Good test coverage (100% test-to-source ratio)
  • Consistent naming conventions (snake_case)
  • Good security practices — no major issues detected
  • Properly licensed project

Weaknesses

  • 1 files with critical complexity need refactoring

Recommendations

  • Add a linter configuration to enforce code style consistency

Languages

erlang
91.1%
yaml
5.3%
markdown
3.6%

Frameworks

None detected

Quality Timeline

1 quality score recorded.

View File Metrics

Embed Badge

Add to your README:

![Quality](https://repos.aljefra.com/badge/708654.svg)
Quality BadgeSecurity Badge
Export Quality CSVDownload SBOMExport Findings CSV