Skip to content

Entrega 2 — JCM - #241

Open
jnchacon wants to merge 2 commits into
LIDR-academy:mainfrom
jnchacon:feature-entrega2-JCM
Open

Entrega 2 — JCM#241
jnchacon wants to merge 2 commits into
LIDR-academy:mainfrom
jnchacon:feature-entrega2-JCM

Conversation

@jnchacon

@jnchacon jnchacon commented Jul 8, 2026

Copy link
Copy Markdown

Entrega 2 — Código funcional (primer MVP ejecutable)
Alumno: Juan Andrés Chacón Matteo
Proyecto: Components DB — Catálogo Estructurado de Componentes Eléctricos

Contenido de readme.md y prompts.md actualizado

  • Sección 6: Tickets de trabajo y desarrollo del MVP
    • CRUD de componentes EAV (Sesión 021 - PR #18 en components-db) con vista dinámica HTMX y persistencia de columnas tipadas.
    • Estructura de árbol documental con django-treebeard y SortableJS (Sesión 022 - PR #19 en components-db).
  • Sección 7: Pull Requests y Features Avanzadas
    • Integración de IA Gemini con PyMuPDF (Sesión 024 - PR #23 en components-db) para extracción de parámetros de catálogos en PDF (datasheets) con google-genai.

Repositorio del proyecto
https://github.com/jnchacon/components-db/tree/feature-entrega2-JCM (privado, ya compartido con la TA)

jnchacon added 2 commits June 9, 2026 22:26
Fill in readme.md template with:
- Project card (Components DB - electrical components catalog)
- Product description (objectives, features, installation)
- Architecture (C4 diagrams, monolithic Django, HTMX+Alpine.js)
- Data model (15-entity ERD with EAV typed columns)
- API specification (3 key endpoints: search, HTMX partials, JSON)
- User stories (3: create component, parametric search, register offer)
- Work tickets (3: backend service, frontend HTMX form, DB models)
- Pull requests (3: #1 PRD, LIDR-academy#3 scaffold, LIDR-academy#6 dev environment)

Fill in prompts.md with key prompts from 11 development sessions
covering product definition, architecture decisions, data modeling,
API design, and implementation planning.
@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

prompts.md and readme.md were both rewritten from placeholder templates into detailed, section-by-section documentation of prompts used across the project lifecycle: idea definition, PRD, architecture, data model, API spec, user stories, MVP tickets, and AI extraction features. No code entities changed.

Changes

Prompt documentation update

Layer / File(s) Summary
Header and index updates
prompts.md, readme.md
Introductions describe tools/skills used (Gemini, Claude), archived conversation links, and expanded section indexes.
Idea definition and PRD prompts
prompts.md, readme.md
Documents prompts for initial idea definition, PRD creation, and resolving PRD open questions.
System architecture prompts
prompts.md, readme.md
Documents prompts for HTMX+Alpine.js stack decisions, C4 diagrams, project structure, infra, security, and testing strategy.
Data model prompts
prompts.md, readme.md
Documents prompts for typed EAV design, ERD generation, and planned data model extensions.
API specification prompts
prompts.md, readme.md
Documents prompts for Django/HTMX route definitions and sequence diagrams for OOB swap flows.
User stories prompts
prompts.md, readme.md
Documents prompts for initial stories, Admin role additions, and critical use-case specs.
MVP ticket prompts
prompts.md, readme.md
Documents prompts for Component CRUD and document tree CRUD with validation rules.
Advanced AI extraction feature prompts
prompts.md, readme.md
Documents prompts for the PyMuPDF+Gemini extraction pipeline, JSON parsing, and EAV traceability tagging.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title is too generic and doesn't describe the documentation updates in readme.md and prompts.md. Rename it to reflect the main change, e.g. documentation updates for Components DB prompts and README content.
✅ Passed checks (4 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@jnchacon jnchacon changed the title Entrega 2 — Juan Andrés Chacón Matteo Entrega 2 — JCM Jul 8, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (2)
readme.md (1)

25-253: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Label the fenced snippets with a language.

These fences are all unlabeled, so markdownlint will keep flagging MD040. Please tag prose blocks as text and the few command/diagram snippets as bash or mermaid so the doc stays lint-clean and easier to scan.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@readme.md` around lines 25 - 253, The readme has multiple fenced code blocks
without language tags, which triggers markdownlint MD040. Update each fenced
snippet in the document by adding the appropriate language identifier based on
its content: use text for narrative/prose examples, bash for shell-style
prompts/commands, and mermaid for diagrams. Focus on the unlabeled fences in the
sections describing the `/define-idea`, `/create-prd`, `/create-srs`,
architecture, ERD, routes, and sequence diagrams so the markdown stays
lint-clean and easier to scan.

Source: Linters/SAST tools

prompts.md (1)

25-253: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Label the fenced snippets with a language.

These fences are all unlabeled, so markdownlint will keep flagging MD040. Please tag prose blocks as text and the few command/diagram snippets as bash or mermaid so the doc stays lint-clean and easier to scan.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@prompts.md` around lines 25 - 253, The fenced snippets in this document are
missing language tags, which triggers markdownlint MD040. Update each unlabeled
fence in the affected prompts/sections to use the appropriate language marker:
prose examples as text, shell-style commands as bash, and architecture/sequence
snippets as mermaid. Keep the content unchanged and ensure the labels are
applied consistently across the /define-idea, /create-prd, /create-srs, and
implementation example blocks so the file stays lint-clean.

Source: Linters/SAST tools

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@prompts.md`:
- Around line 25-253: The fenced snippets in this document are missing language
tags, which triggers markdownlint MD040. Update each unlabeled fence in the
affected prompts/sections to use the appropriate language marker: prose examples
as text, shell-style commands as bash, and architecture/sequence snippets as
mermaid. Keep the content unchanged and ensure the labels are applied
consistently across the /define-idea, /create-prd, /create-srs, and
implementation example blocks so the file stays lint-clean.

In `@readme.md`:
- Around line 25-253: The readme has multiple fenced code blocks without
language tags, which triggers markdownlint MD040. Update each fenced snippet in
the document by adding the appropriate language identifier based on its content:
use text for narrative/prose examples, bash for shell-style prompts/commands,
and mermaid for diagrams. Focus on the unlabeled fences in the sections
describing the `/define-idea`, `/create-prd`, `/create-srs`, architecture, ERD,
routes, and sequence diagrams so the markdown stays lint-clean and easier to
scan.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0069e768-9442-4d3e-b6ea-a5d32c0d3504

📥 Commits

Reviewing files that changed from the base of the PR and between bcde5c4 and 065061b.

📒 Files selected for processing (2)
  • prompts.md
  • readme.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant