菜单
Git commit/push discipline specific to Target Pathogen Web — fetch-and-compare before committing, exact-filename staging (never git add -A), commit message format, and push behavior. Load before committing or pushing changes in this repo.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/sndg-arg/targetpathogenweb --skill tpw-git-workflow命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Layout-fusion standard for Target Pathogen Web — removes the "stacked separately-boxed cards floating on a gray canvas" pattern by merging page-level sections onto one continuous white background with hairline dividers, while keeping the site's rounded-corner geometry, Space Grotesk headings, and pill-shaped chips/buttons exactly as they are. Load before restructuring any page's top-level layout (multiple `.tp-ui-panel`/`.tp-card` sections stacked with gaps between them). Composes with tpw-frontend-styling (token/hex/verification rules) — load both for CSS work.
Django view/service architecture conventions for Target Pathogen Web — service-layer separation, prefetch reuse, the genome-scoped caching pattern, safe deduplication of copy-pasted helpers, and how to verify backend changes without a local execution environment. Load before editing files under tpweb/views/ or tpweb/services/.
Design-token, CSS, and Django-template conventions for Target Pathogen Web. Load before editing any file under static/css/pages/, static/css/components/, or tpweb/templates/ — covers the hex-color rule, the token inventory, reusable component idioms (stat cards, panels, chips), dark mode, motion, cache-busters, and how to verify a template/CSS change without a local execution environment. For Cytoscape.js graph rendering specifically (static/js/pages/metabolic-*.js), load tpw-metabolism-graphs instead/in addition.
基于 SOC 职业分类
| name | tpw-git-workflow |
| description | Git commit/push discipline specific to Target Pathogen Web — fetch-and-compare before committing, exact-filename staging (never git add -A), commit message format, and push behavior. Load before committing or pushing changes in this repo. |
Run git fetch origin <branch> and compare HEAD against origin/<branch> in both directions
(git log --oneline HEAD..origin/<branch> and git log --oneline origin/<branch>..HEAD) to
confirm there's no divergence before proceeding. Don't skip this even for a small change — it's
cheap and catches a stale local branch before it turns into a conflicted push.
Stage only the specific files intentionally changed, by exact name (git add path/to/file.py path/to/other.css). Never git add -A or git add . in this repo. The user routinely keeps
personal, in-progress working documents sitting modified or untracked in the working tree —
observed examples: docs/TARGET_ROADMAP.md, docs/TARGET_FUNCTIONAL_REPORT.md. These must never
be swept into a commit unless the user explicitly asked for that specific file to be included.
Run git status --short after staging to confirm only the intended files are staged.
In practice docs/TARGET_ROADMAP.md gets updated and committed often — the rule above is about
never including it by accident via broad staging, not about avoiding it. When a code change
completes or corrects a roadmap item (or the user directly asks to update the roadmap), edit and
stage it explicitly by name like any other intentionally-changed file.
Concise, explains why the change was made, not just what changed. Do not add a
Co-Authored-By: Claude trailer — the user asked for commits in this repo to not carry that
line. Pass the message via a heredoc, per standard git-commit discipline.
Push after committing without re-asking each time — this has been the established convention for this repo/session. This does not extend to force-pushing or amending a commit that's already been pushed — those remain "ask first" actions regardless of this convention, per the general git-safety rules (never skip hooks, never force-push without explicit request, never amend published history).