Repository navigation
[Preset]: Add db-standards #4654
Description
Activity
Hi @gdakuzak,
Thank you for submitting this comprehensive preset! The database standards, motor-specific on-demand loading, and clean stacking mechanism via
appendlook excellent and well-structured.Before we proceed with the official approval and integration, could you please clarify or double-check a couple of quick technical details?
- Preset Stability: I noticed the preset is currently at version
0.8.2while requiringspec-kitversion0.1.0. Since it's below1.0.0, do you consider the current schema definition stable enough for production environments, or are there breaking changes planned soon? - Command Collision: The preset introduces the custom command
speckit.constitution. We just want to ensure this naming convention doesn't collide with other existing global presets or core commands within the ecosystem. - Manifest Validation: We will trigger a local test run via
specify preset add --from <download-url>shortly to verify thepreset.ymlintegrity and the README documentation layout.
Looking forward to your feedback so we can move this forward!
Best regards.
Reacted by Guilherme Dakuzaku- Preset Stability: I noticed the preset is currently at version
hey @edenperez909-eng !
Thanks for your feedback!
Preset Stability: I noticed the preset is currently at version 0.8.2 while requiring spec-kit version 0.1.0. Since it's below 1.0.0, do you consider the current schema definition stable enough for production environments, or are there breaking changes planned soon?
Yes, I have a few ideas for changes, but they're more focused on engine presets rather than the standardization that was established.
Command Collision: The preset introduces the custom command speckit.constitution. We just want to ensure this naming convention doesn't collide with other existing global presets or core commands within the ecosystem.
The preset only appends a "Database Confirmation" step (engine, version, migration tool, data-protection posture) to it, via
strategy: "append". It doesn't replace the core behavior or add a new command.Manifest Validation: We will trigger a local test run via specify preset add --from shortly to verify the preset.yml integrity and the README documentation layout.
Okay, if you need any changes, I'm available to make them.
Best regards.
cc @github/spec-kit-maintainers — new catalog submission for review.
Validation failed for the community preset submission.
- Release and download URL validation: failed. The pinned URL and tag are valid (v0.8.2 matches version 0.8.2), and the GitHub release exists, but the required HTTP 200 archive fetch could not be performed in this workflow environment because outbound curl requests are blocked. A repository/release metadata check cannot substitute for downloading the archive, so this check cannot pass.
Other checks passed: the [Preset]: title, preset ID and version formats, public repository, preset.yml and LICENSE, GitHub README URL and install commands, repository ownership/pinned URL format, and all required checklist boxes. No catalog or documentation changes were made. Please resubmit or rerun the validation in an environment that can fetch the archive URL.
Generated by 🎨 Add Community Preset from Issue Submission for #4654 · copilot · gpt52codex · 1.59 AIC · ⌖ 6.34 AIC · ⊞ 23.8K · ◷
@KSchlobohm or @edenperez909-eng
The "Release and download URL validation" check failed only because outbound curl is blocked in the workflow environment. The pinned URL returns HTTP 200 on my side (tag v0.8.2, release exists). Could a maintainer verify it manually or re-run the check? Is there anything else I need to change on my side?Hey everyone!
Is there anything else I need to change on my side ?
Thanks- added a commit that references this issue
on Sep 23, 2026 Pull request created: #4702
Generated by Add Community Preset from Issue Submission · copilot · gpt52codex · 2.48 AIC · ⌖ 12.1 AIC · ⊞ 24.7K
- added a commit that references this issue
on Sep 23, 2026 @gdakuzak thanks for your contribution. the preset is now added to the catalog.
Reacted by Guilherme DakuzakuThank you for your support. I want to continue contributing more to the spec-kit!
Reacted by Ken Schlobohm
Preset ID
db-standards
Preset Name
Database Standards
Version
0.8.2
Description
Database conventions for spec-driven work: naming, data-model design, constraints, data protection, performance, query safety, a schema-review checklist, and engine-specific references. ORM-agnostic.
Author
Guilherme Dakuzaku
Repository URL
https://github.com/gdakuzak/spec-kit-preset-db-standards
Download URL
https://github.com/gdakuzak/spec-kit-preset-db-standards/archive/refs/tags/v0.8.2.zip
Documentation URL
https://github.com/gdakuzak/spec-kit-preset-db-standards/blob/main/README.md
License
MIT
Required Spec Kit Version
0.1.0
Required Extensions (optional)
None
Templates Provided
Commands Provided
Number of Scripts (optional)
No response
Tags
database, standards, data-modeling, performance
Key Features
append, so it stacks cleanly with other presetsTesting Checklist
specify preset addSubmission Requirements
preset.ymlmanifest includedspecify preset add ...command (preferablyspecify preset add --from <download-url>using the exact download URL)