docs(ai): add AI prompt template guide for engineering tasks#38
docs(ai): add AI prompt template guide for engineering tasks#38
Conversation
Add a structured prompt template to help engineers write clear, well-scoped problem statements when using AI coding tools. Includes filled-in examples for adding features, fixing bugs, and refactoring, along with writing tips, common mistakes to avoid, and a quick checklist. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: David Deal <ddeal@linuxfoundation.org>
There was a problem hiding this comment.
Pull request overview
This PR adds a new documentation file (ai/ai-prompt-template.md) to the ai/ directory, providing a structured prompt template guide for engineering teams using AI coding tools. It fits alongside existing AI-related documentation such as model lists, review guides, and CLI tooling docs.
Changes:
- Adds a reusable prompt template with sections for Task Title, End State, Context, Constraints, and Acceptance Criteria
- Includes three filled-in examples covering feature addition, bug fixing, and refactoring scenarios
- Provides writing tips, common mistakes to avoid, and a quick pre-submission checklist
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (7)
✅ Files skipped from review due to trivial changes (3)
WalkthroughAdds a new AI prompt template document and applies markdown formatting adjustments across several docs: updates to .markdownlint rules and multiple README/guide files where tables, line-wrapping, and minor whitespace were changed. No functional code or public API changes. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment Tip You can disable sequence diagrams in the walkthrough.Disable the |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
ai/ai-prompt-template.md (1)
215-224: Add an explicit markdownlint checklist item.Since linting Markdown is a required repo rule, add a checkbox that explicitly confirms
markdownlint-cli2was run.As per coding guidelines, "All Markdown documentation must pass markdownlint validation" and "Lint Markdown files using markdownlint-cli2 ... before committing."Suggested diff
## Quick Checklist Before submitting your prompt, verify: - [ ] End state describes a specific, observable result - [ ] Context identifies the relevant files, modules, or areas of the codebase - [ ] Constraints define what must not change and what standards apply - [ ] Acceptance criteria are concrete and verifiable - [ ] The scope maps to a single, reviewable unit of work - [ ] Any referenced conventions or patterns include a pointer to an example in the codebase +- [ ] `markdownlint-cli2 ai/ai-prompt-template.md` passes with no errors🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@ai/ai-prompt-template.md` around lines 215 - 224, Add an explicit checklist item under the "Quick Checklist" section to confirm markdown linting was executed: update the checklist (the block beneath the "## Quick Checklist" header) to include a checkbox like " - [ ] markdownlint-cli2 was run and all files pass" so reviewers can verify that markdownlint-cli2 was run and passed before submitting the prompt.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@ai/ai-prompt-template.md`:
- Around line 215-224: Add an explicit checklist item under the "Quick
Checklist" section to confirm markdown linting was executed: update the
checklist (the block beneath the "## Quick Checklist" header) to include a
checkbox like " - [ ] markdownlint-cli2 was run and all files pass" so reviewers
can verify that markdownlint-cli2 was run and passed before submitting the
prompt.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: fa1151dd-1f7a-43c6-870a-51691655f607
📒 Files selected for processing (1)
ai/ai-prompt-template.md
- Wrap long line in lfx_one/ko-build.md (MD013) - Fix table separator row spacing in lfx_one/secrets-management.md (MD060) - Exclude code blocks from MD013 line-length checks in .markdownlint.json Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: David Deal <ddeal@linuxfoundation.org>
- Exclude tables from MD013 line-length checks (URLs can't be wrapped) - Wrap long prose paragraphs in expectations/roles-and-responsibilities.md - Reformat table in expectations/roles-and-responsibilities.md to compact style - Fix table separator spacing in lfx_one/skills references (MD060) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: David Deal <ddeal@linuxfoundation.org>
Summary
ai/ai-prompt-template.mdwith a structured prompt template for engineering tasksTest plan
🤖 Generated with Claude Code