git-context-guardrails

To enforce architecture guardrails before proposing code changes, you must read architecture docs, identify target files, scan git history, and produce a mandatory findings report validating feasibility within existing patterns.

An architecture findings report for production-grade code planning is a mandatory summary of patterns, components, and historical decisions extracted from git history and docs to validate implementation feasibility before planning.

Yes, you need existing architecture docs to use git context guardrails, because the process requires reading these docs and gathering historical context to produce a standardized plan adhering to established patterns.

The best way to align new implementation tasks with existing system patterns is to extract reusable context from git history and architecture docs, generating a mandatory findings report to guide production-grade solutions.

Your implementation plan fails to match production-grade architecture standards when it skips the mandatory findings report, bypassing the required review of architecture docs and git history needed to enforce guardrails.

To extract reusable context from git history for code review, you must perform a prescribed git history scan to locate target files, review past architectural decisions, and document findings before proposing tasks.