allra-database-schema
Design Reliable JPA and QueryDSL Data Layers
Inconsistent persistence patterns create fragile repositories, transaction errors, and inefficient entity relationships. This skill applies Allra standards to JPA, QueryDSL, and Spring transactions.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "allra-database-schema" from https://skillstore.io/skills/allra-fintech-allra-database-schema.md and its manifest at https://skillstore.io/api/skills/allra-fintech-allra-database-schema/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "allra-database-schema". Review a user search repository that queries users by email and name.
Expected outcome:
- Keep the query under the user repository because User is the primary From entity.
- Use nullable BooleanExpression predicates for optional email and name filters.
- Return a dedicated summary projection instead of loading complete entities.
Using "allra-database-schema". Choose transaction settings for list, create, and activate service methods.
Expected outcome:
- Mark list operations as read-only transactions.
- Use writable transactions for create and activate operations.
- Declare the transaction annotation explicitly on each public service method.
Using "allra-database-schema". Review an order-to-user and order-to-items mapping.
Expected outcome:
Use lazy loading for the user association. Maintain both sides when adding items, and confirm cascade deletion matches business requirements.
Security Audit
High RiskAll 29 static findings are false positives caused by Markdown code fences, inline code, QueryDSL fetch operations, and ordinary Java domain methods. A separate high-severity issue remains because the examples assign a supplied password directly to an entity without demonstrating hashing.
Confirmed security concerns (1)
Risk Factors
โ๏ธ External commands (24)
๐ Network access (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/allra-fintech-allra-database-schema/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/allra-fintech-allra-database-schema?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/allra-fintech-allra-database-schema?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/allra-fintech-allra-database-schema/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/allra-fintech-allra-database-schema.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
Allra-Fintech. (2026). allra-database-schema security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/allra-fintech-allra-database-schema/audits/9BibTeX citation
@techreport{allra-fintech-allra-fintech-allra-database-schema-2026,
author = {Allra-Fintech},
title = {allra-database-schema security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/allra-fintech-allra-database-schema/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "allra-database-schema security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "Allra-Fintech"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/allra-fintech-allra-database-schema/audits/9"
identifiers:
- type: other
value: "skillstore:allra-fintech-allra-database-schema:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Create a New Persistence Model
Generate a JPA entity, repository, relationships, and transaction-aware service methods for a new domain feature.
Standardize QueryDSL Repositories
Review repository placement, support interfaces, predicates, and DTO projections against Allra conventions.
Audit Transaction Boundaries
Classify service operations as read-only or writable and identify missing @Transactional declarations.
Try These Prompts
Create a JPA entity for [domain object] with these fields: [fields]. Apply the Allra entity and relationship conventions.
Create QueryDSL repository support for [entity] to filter by [conditions] and return [DTO fields]. Explain the repository placement.
Review these service methods: [methods]. Assign suitable @Transactional settings and explain which methods must remain writable.
Refactor this persistence layer: [design]. Check QueryDSL ownership, projections, transaction boundaries, lazy relationships, and database compatibility. List unresolved risks.
Best Practices
- Verify generated mappings and queries against the active database engine and version.
- Use repository interfaces from services and keep implementation classes behind those interfaces.
- Hash credentials before persistence and never copy raw password examples into production.
Avoid
- Do not inject QueryDSL implementation classes directly into services.
- Do not mark write operations as read-only transactions.
- Do not use eager relationships or broad cascades without validating access and deletion behavior.
Frequently Asked Questions
Which technology versions does this skill target?
Is QueryDSL required?
Where should a QueryDSL query be defined?
When should readOnly be enabled?
Does this skill guarantee database portability?
Can I use the password example unchanged?
Developer Details
Author
Allra-FintechLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Repository
https://github.com/Allra-Fintech/allra-ai-skills/tree/main/backend-plugin/skills/database-schemaRef
31bc7611b504c197d3e993aef7943461c871616f
Maintenance freshness
7/26/2026
Usage
6 downloads ยท 212 views
File structure
๐ SKILL.md