[NF-7V1] A rejected CSV

Closed Beginner friendly
#232 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #256 by @elfekimuhammed — merged

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
80/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
html, python

Research direction

Read partials/ai_prompt.html and the planning doc 7V-more-ai-prompt-buttons.md, plus ai/ARCHITECTURE.md for context. Add the why-this-helps line and Arabic string to the partial, wire it into mapping/review screens, and add a test that prompt text is never open. Done when buttons appear on row failure and test passes.

Written by the indexing model from the issue text.

Description

coins:500 kind:new-feature pillar:understand
Code

NF-7V1

What to build (More AI prompt buttons that carry Lightning's context)

On the mapping and review screens, when rows fail, a prompt holding the file's header, the error lines and the schema, so the AI fixes the file instead of the person. Built from names and categories only, never amounts unless the person exports them. Use partials/ai_prompt.html, add a one-line why-this-helps and its Arabic string, and a test that the prompt text is never open on the page.

Context

Owner, 2026-10-30: every AI hand-off is two buttons, Copy prompt and Edit prompt, never the text (done for the statement import, the workbook setup and Export for AI; one partial, partials/ai_prompt.html). Each says why it helps: the prompt carries context an AI tool cannot guess. Five screens would use one; this is one of them.

Read first

7-planning-import-and-search/7V-more-ai-prompt-buttons.md · financial rules in ai/ARCHITECTURE.md (figures are computed in Python services, never templates).

Reward: 500 Lightning Coins once a pull request that says Closes #<this issue> is merged. To work on it: comment /take. Setup: CONTRIBUTING.md.

Dominant language
Python
Stars
1
Forks
0
Avg merge
2h 8m
Merged PRs (30d)
248

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LightningEg/Lightning

All issues in LightningEg/Lightning

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.