vitya
afca818a05
Нечего настраивать (решение 14/15). Свип ссылок: project-bootstrap v2.1.0 (Steps 3/4 → mappa, манифест без setup-строк), project-discipline (Rule 1), setup-projects-meta README, using-tasks/using-wiki README.
project-discipline
Policy skill that codifies four cross-project discipline rules so the same guarantees that hold in a tightly-maintained repo apply everywhere.
When it triggers
- Session start — when
AGENTS.mdcontains the linefollow project discipline(added byproject-bootstrapv2.0.0+). - In-chat — when the user says "use project discipline", "соблюди дисциплину", "проектные правила", or close variants.
The four rules
- Project conventions over skill defaults.
AGENTS.md/.wiki/CLAUDE.md/.tasks/override any other skill's defaults. Specs go to.wiki/concepts/, tasks to.tasks/. - Master-only. All work on
master(ormain). No feature branches without explicit user approval. - Semver discipline. Bump
version:inSKILL.md/package.json/pyproject.tomlon every edit per MAJOR / MINOR / PATCH; record in commit message; rebuilddist/artifacts after. - Push freely by default. No confirmation needed for push; a local push-gate skill (e.g. books — auto-deploy) overrides per project. Force / delete / non-ff push always asks.
Prerequisites
None. The skill is a textual policy document; it takes no actions and has no
external dependencies. Activate it by adding follow project discipline to
AGENTS.md (or use project-bootstrap v2.0.0+ which adds it automatically).
Related
project-bootstrap(v2.0.0+) — adds the trigger line to new and existing projects'AGENTS.md.pulling-before-work— companion skill activated by the canonical template; pulls origin once at session start (git pull --ff-only).using-tasks/using-wiki— the format conventions Rule 1 routes work into..wiki/concepts/project-discipline-design.md(inskills) — full design rationale.