flask-debug-cross-worktree-edit-stale SKILL.md skillB
flask-debug-cross-worktree-edit-stale from wan-huiyan/agent-traffic-control is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wan-huiyan/agent-traffic-control/flask-debug-cross-worktree-edit-stale@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wan-huiyan/agent-traffic-control
- Path
plugins/agent-traffic-control/skills/flask-debug-cross-worktree-edit-stale/SKILL.md- Versions recorded
- 4
- Latest version
- v1.0.0, committed Aug 11, 2026
- First version recorded
- May 13, 2026
- Size
- 9,522 bytes
- Repository stars
- 3
- License
- MIT
Diagnose "I edited the template / view / CSS but Flask debug-mode keeps serving the old version" when running a local dev server (Flask, Django runserver, Rails server, etc.) from one git worktree while editing files in a sibling worktree of the same repo. Use when: (1) you have multiple `git worktree` checkouts of the same repo (typical with `.claude/worktrees/<feature>` directories), (2) a dev server is running in worktree A serving its working tree, (3) you're making edits in worktree B…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Flask debug edits cross-worktree stale ## Problem You're running a Flask dev server (`python app.py` with `debug=True`, or `flask run --debug`) from one git worktree. You're editing template / static / view files from a *sibling* worktree of the same repo, because the branch you want to ship is checked out at the running worktree and `git checkout <branch>` fails in your editing worktree. You hit `curl http://127.0.0.1:PORT/the-page` after each edit, and the response bytes don't change. You hypothesize Jinja bytecode cache, Flask `@_ttl_cache`, browser caching, CDN, or stale `__pycache__`. You try `touch app.py` to bust Flask's debug-reload, restart the process, clear browser cache. Nothing fixes it. **Root cause:** git worktrees have **independent working trees on disk**. Each `git worktree` directory has its own copy of every tracked file. Flask is reading from `<worktree-A>/templates/page.html`. Your edits live in `<worktree-B>/templates/page.html`. They're physically different files; the dev server has no way to see B's edits until A's disk state changes. ## Trigger conditions (high-confidence diagnosis) Fire this skill when ALL of these are true: …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/flask-debug-cross-worktree-edit-stale@sha256:cd57462d0c00f4acThe line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_a2t2xicle3dqtqnp)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 13, 2026 and Aug 11, 2026, about one every 30 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-11 | f274e4b | 9,522 B | B | view · diff |
| v1.0.0 | 2026-08-05 | e3930cf | 9,527 B | B | view · diff |
| v1.0.0 | 2026-07-08 | f1254dd | 9,763 B | B | view · diff |
| v1.0.0 | 2026-05-13 | 07472bf | 9,724 B | B | view |
Audit of the latest version
- fail: No link to a raw IP address (matched: http://127.0.0.1)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9522 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
wan-huiyan/agent-traffic-control · 3 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_a2t2xicle3dqtqnp GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/flask-debug-cross-worktree-edit-stale GET https://markdownregistry.com/api/v1/blob/cd57462d0c00f4ac8a5e80605250bea88913ed007b4cc24b263efec32950c2f4
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.