pallets-jinja-bugfix

name	pallets-jinja-bugfix
description	Expert bug-fixing skills optimized for the pallets/jinja repository. Contains repo-specific patterns, diagnostic strategies, and step-by-step workflows for efficiently finding and resolving bugs in this codebase. Use when debugging issues, fixing failing tests, or resolving reported bugs.

TERMINAL / BASH WORKFLOW

• Always operate on the main repo at /testbed. Before/after changes, confirm with:
  • git -C /testbed status
  • git -C /testbed diff (Avoid running git in nested directories like /testbed/src/jinja2 unless you’ve confirmed /testbed itself isn’t the git root.)
• Quick codebase navigation patterns:
  • ls /testbed/src/jinja2
  • find /testbed/src/jinja2 -maxdepth 1 -type f | sort
  • grep -RIn "revindex" /testbed/src/jinja2
  • grep -RIn "parse_filter" /testbed/src/jinja2
• When output is too long, slice it:
  • sed -n '900,980p' /testbed/src/jinja2/parser.py
  • head -n 60 file ; tail -n 60 file

REPO-SPECIFIC KNOWLEDGE (JINJA2 IN THIS REPO)

• The package under test is the in-repo implementation: /testbed/src/jinja2 (not the system/site-packages install).
  • Do NOT “fix” by moving/renaming /testbed/src/jinja2 or by pip-installing a different Jinja2 version; pytest expects to import the local package.
• Common bug locations:
  • Parsing / filters / tests: src/jinja2/parser.py
  • Loop variables (loop.index, loop.revindex, etc.): src/jinja2/runtime.py (LoopContext)
  • Environment compilation and template loading: src/jinja2/environment.py
  • Tokenization: src/jinja2/lexer.py
• Tests live under /testbed/tests. Use them to confirm behavior and prevent regressions.

DEBUGGING STRATEGY (REPEATABLE)

• Reproduce first with a minimal snippet using the local code: