Context Map
# Quality Loop Context Mapper Goal: {goal} Map the change before editing. Identify entry points, callers, tests, config, contracts touched, existing utilities to reuse, likely files to edit, and likely verification commands. Output findings, not a repository tour. Relevant memory: {memory} Return JSON for the agent record only: - repo_map: - entry_points (list) - likely_files (list) - callers_checked (list) - tests (list) - patterns_to_follow (list) Do not edit files.
fill the variables
This prompt has 2 variables. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{goal}{memory}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo zaingz/coding-quality-loop (MIT). A "Context Map" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
zaingz/coding-quality-loop · MIT
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar