Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Deliverable guide
Code Review Feedback source-backed Guide
Defines source-backed change intent, correctness, security, reliability, test, compatibility, maintainability, severity, evidence, suggestion, and review-decision feedback, evidence handling, and action.
Read the fileOverview
Code Review Feedback Overview
source-backed deliverable bundle for change intent, correctness, security, reliability, test, compatibility, maintainability, severity, evidence, suggestion, and review-decision feedback, evidence.
Read the fileWorkflow
Code Review Feedback source-backed Triage
1. State the decision and direct answer possible now. 2. Record Verified, Provided, Assumed, and Needs verification separately. 3.
Read the fileQuality rubric
Code Review Feedback source verification Check
A passing response contains all five required sections, names a source URL, preserves prompt evidence, avoids invented provenance and reviewer ownership, and names these prohibited actions.
Read the fileIs this bundle right for your task?
Who it is for
- People drafting, reviewing, approving, or relying on Code Review Feedback
- Teams working in Technology, Business operations
When to use it
- A Code Review Feedback draft needs a clear purpose, audience, evidence base, structure, and approval path.
- An existing draft needs unsupported claims, missing sections, unresolved decisions, and reviewer comments addressed.
What you need to provide
- The document purpose, audience, source evidence, required sections, constraints, approvers, and intended decision or action.
- Existing drafts, templates, policies, examples, terminology, and review criteria that the output must follow.
Tasks and expected outputs
Questions it helps answer
- Prepare a code review feedback review brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready decision with explicit verification and approval boundaries.
What it helps produce
- Code Review Feedback review brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the document purpose, audience, source evidence, required sections, constraints, approvers, and intended decision or action. Ask the agent to draft or review Code Review Feedback and return Code Review Feedback review brief with material claims tied to evidence and assumptions, open questions, reviewers, and approval gates marked. Begin with GitHub Docs — Get Started / Reviewing Pull Requests Quickstart, then confirm that the reference is current and applicable. Inspect Code Review Feedback source-backed Guide before drafting.
Context path: bundles/deliverables/code-review-feedback
What the bundle includes
Frameworks
- source-evidence matrix
- qualified-review gate
Evaluations
- Code Review Feedback source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Publishing, approving, or acting on a draft before its material claims, source evidence, owners, and approval gates have been reviewed.
Known limitations
- Use the listed authoritative or identified source surfaces for general Code Review Feedback guidance; local facts, records, values, states, permissions, and results require inspected evidence.
- Task-specific work requires current evidence for repository and branch, change request and acceptance criteria, full diff and surrounding code, language and runtime, architecture and threat context, tests and results, static or security analysis, logs, backward-compatibility requirements, deployment and rollback plan, ownership and review policy, exact file and line, reproduction evidence, confidence, and approvals.
- Do not infer change intent, runtime behavior, defect, exploitability, severity, test result, compatibility, merge eligibility, or deployment safety.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, health, student, and other sensitive data.
- Require explicit confirmation before actions that submit review comments, approve or request changes, apply suggestions, edit code, run commands or tests, merge changes, expose private code or secrets, or deploy software.
- Route legal, privacy, security, compliance, financial, employment, clinical, safety, and other qualified judgments to an evidenced accountable reviewer.