it4r-agent-kit
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
02 资源文件 9
- 参考文档.claude-plugin/marketplace.json625 B
- 参考文档.claude-plugin/plugin.json411 B
- 参考文档AGENTS.md10.1 KB
- 参考文档CLAUDE.md1.0 KB
- 脚本hooks/check-secrets.sh6.7 KB
- 脚本hooks/credential-guard.sh5.4 KB
- 参考文档hooks/hooks.json635 B
- 许可证LICENSE.txt1.0 KB
- 参考文档README.md9.9 KB
03 SKILL.md 正文
skills/it4r-conventions/SKILL.md
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.
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.
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.