Quality Checks and Git Hooks Setup

Shared project skill-context

Before mode routing or work, read existing files relative to the current project root in this order (reuse them if already loaded):

1. .ai-factory/skill-context/global-skill-context.md, all bundled skills.
2. .ai-factory/skill-context/aif-quality-setup/SKILL.md, this skill.

Missing files are skipped; an existing unreadable file stops dependent work with its path. Precedence: individual > build (when applicable) > global > skill defaults; retain non-conflicting instructions and check all outputs against the effective rules. These layers customize workflow; they do not replace the project's rules/architecture hierarchy or relax explicit requirements, ownership, scope, safety/privacy, validation, or approval boundaries. Report conflicts with those boundaries instead of overriding them. global is a project-local layer, not home-directory configuration. Custom/extension skills do not automatically use it.

Detect the actual project before proposing tools. Language profiles supply relevant knowledge after discovery; they are not a menu the user must select manually. Support existing and new JS/TS, PHP, Python and Rust setups, mixed monorepos and multiple repositories. For other stacks, investigate native tools and current official documentation; unresolved compatibility remains explicit.

Step 0: Resolve Context and Scope

Read .ai-factory/config.yaml when present, without creating or updating it:

• paths.description → .ai-factory/DESCRIPTION.md
• paths.architecture → .ai-factory/ARCHITECTURE.md
• paths.rules_file → .ai-factory/RULES.md
• paths.rules → .ai-factory/rules/; rules.base → .ai-factory/rules/base.md
• named rules.<area> entries for the selected components
• language.ui → en; language.artifacts → UI language; language.technical_terms → keep (unknown/legacy values also use keep)
• git.enabled → true