sync-agent-rules
Use when the user wants to install, vendor, update or re-sync the shared ENAC IT4R rules (it4r-agent-kit's AGENTS.md) in the current repo — "sync agent rules", "update the IT4R rules", "vendor the kit" — after a kit release, or when a repo has no IT4R rules file yet. Pins the copy to the kit's current main commit, wires CLAUDE.md and Copilot on first setup, and summarizes what changed upstream.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- sync-agent-rules
- description
- Use when the user wants to install, vendor, update or re-sync the shared ENAC IT4R rules (it4r-agent-kit's AGENTS.md) in the current repo — "sync agent rules", "update the IT4R rules", "vendor the kit" — after a kit release, or when a repo has no IT4R rules file yet. Pins the copy to the kit's current main commit, wires CLAUDE.md and Copilot on first setup, and summarizes what changed upstream.
02 资源文件 1
- 脚本sync-agent-rules.sh1.1 KB
03 SKILL.md 正文
Sync the IT4R rules into this repo
The rules are vendored: a committed copy of the kit's AGENTS.md, so every
contributor and every tool gets them without installing anything. This skill
creates that copy or refreshes it.
1. Find the current state
grep -rl "Vendored from https://github.com/EPFL-ENAC/it4r-agent-kit" --include='*.md' .
Found a copy: refresh it (step 2). None: set it up (step 3).
2. Refresh
- If the repo has a
sync-agent-rulesMake target, runmake sync-agent-rules. Otherwise, run the script from this skill's directory (${CLAUDE_PLUGIN_ROOT}/skills/sync-agent-rules/under a plugin install, otherwise the directory thisSKILL.mdwas read from):
Both write the same file: Copilot frontmatter, a header pinning the kit commit, thenbash "<this skill dir>/sync-agent-rules.sh" <path-of-the-copy>AGENTS.mdat that commit. - Read the
git diffof the copy and tell the user, in a few bullets, which rules were added, changed or removed upstream. Then go to step 4.
3. First setup
This follows the README's "Vendored into one project" steps.
- Pick the path:
docs/src/contributing/it4r-rules.mdif the repo has an MkDocsdocs/src/; otherwise ask. Run the script with that path. CLAUDE.md: add@<path>above the project's own rules. Create the file if it's missing.- Copilot: link the copy as
.github/instructions/it4r-agent-kit-rules.md.instructions.mdwith a relative symlink. The copy already carriesapplyTo: "**". Makefile(if there is one): add thesync-agent-rulestarget from the kit README, withAGENT_RULESpointing at the path, so teammates without the plugin can refresh too.- The project's own rules file: tell the user which of its lines the kit now covers. Don't delete them yourself.
4. Finish
- Never edit the vendored copy by hand. A fix goes upstream; see the
sync-memory-upstreamskill. - Don't commit unless asked. Suggested message:
docs: sync IT4R agent rules to <sha>.
04 同仓库更多 Skills
tps
Use when orchestrating multi-ticket work with parallel builder agents in git worktrees, in the spirit of the Toyota Production System. Covers station roles and model choice, the shape of a ticket, rules for builders, the merge flow, verification by raw output and a browser check, the status loop, and when to stop and ask the human.
sync-memory-upstream
Use when the user wants to promote lessons from an AI agent's per-repo memory into it4r-agent-kit — "sync memory upstream", "update the kit from memory", "what did the agents learn that the team should know" — or after a session that saved several feedback memories. Sorts each memory into team rule, project rule, personal preference or state, drafts AGENTS.md and skill edits on a kit branch with one cost line per rule, and never pushes without the user's go.
review-copilot-comments
Fetch automated bot review comments (Copilot, github-actions, GitHub Advanced Security / CodeQL) for the current branch's PR, then produce a prioritized action checklist that filters out nitpicks and groups substantive feedback by file.
plan-conventions
Use when opening or writing a GitHub issue, starting work on an issue, writing or updating an implementation plan or ADR, or judging whether a doc in the repo can be trusted. Covers the ENAC IT4R issue title and TL;DR convention, the source-of-truth hierarchy, plan file naming and frontmatter (status/issue/last_updated/summary), where plans and review notes live, and when a plan must be backfilled.
it4r-conventions
Use when writing or reviewing code in an EPFL ENAC IT4R project — FastAPI + SQLModel + Alembic backends, Vue + Quasar + TypeScript frontends. Holds the team's architecture invariants (backend is source of truth, route → service → repo, no silent fallbacks, frontend never checks roles), style rules, performance budget, and plan/PR workflow.
it4r-agent-kit
暂无简介