ai-factory 2.8.1 → 2.9.0

package/README.md

@@ -10,7 +10,7 @@
   </a>
 </p>
 
-![logo](https://github.com/lee-to/ai-factory/raw/2.x/art/promo.png)
+![logo](https://github.com/lee-to/ai-factory/blob/2.x/art/aif1.jpg)
 
 # AI Factory
 
@@ -174,10 +174,20 @@ AI Factory can generate and maintain your project docs with a single command:
 | [Security](docs/security.md) | Two-level security scanning for external skills |
 | [Extensions](docs/extensions.md) | Writing and installing extensions — commands, injections, MCP, agents |
 | [Configuration](docs/configuration.md) | `.ai-factory.json`, MCP servers, project structure, best practices |
+| [Config Reference](docs/config-reference.md) | Full `config.yaml` key reference and skill read/write matrix |
 
 ---
 
-![happy](https://github.com/lee-to/ai-factory/raw/2.x/art/happy.png)
+![happy](https://github.com/ilhm344/ai-factory/blob/2.x/art/aif2.jpg)
+
+## AIF Handoff
+
+Looking for an **Autonomous Kanban board where AI agents plan, implement, and review your tasks**? Check out [aif-handoff](https://github.com/lee-to/aif-handoff) — a visual task management system built on top of AI Factory.
+
+![ui-light](https://github.com/lee-to/aif-handoff/blob/main/art/ui-light.png)
+![ui-dark](https://github.com/lee-to/aif-handoff/blob/main/art/ui-dark.png)
+![ui-light-list](https://github.com/lee-to/aif-handoff/blob/main/art/ui-light-list.png)
+![ui-dark-list](https://github.com/lee-to/aif-handoff/blob/main/art/ui-dark-list.png)
 
 ## Links
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-factory",
-  "version": "2.8.1",
+  "version": "2.9.0",
   "type": "module",
   "description": "CLI tool for automating AI agent context setup in projects",
   "main": "dist/cli/index.js",

package/skills/aif/SKILL.md

@@ -116,6 +116,145 @@ Check $ARGUMENTS:
 
 ---
 
+## Language Resolution
+
+After creating DESCRIPTION.md, resolve the project language settings.
+
+**Resolution order:**
+1. `.ai-factory/config.yaml` → use `language.ui` and `language.artifacts` if present
+2. `AGENTS.md` → look for language hints in comments or content
+3. `CLAUDE.md` → look for language preferences
+4. `RULES.md` → look for language rules
+5. Ask user if not found
+
+**Questions to ask (if config.yaml doesn't exist):**
+
+```
+AskUserQuestion: What language should I use for communication and artifacts?
+
+Options:
+1. English (en) — Default
+2. Russian (ru)
+3. Chinese (zh)
+4. Other — specify manually
+```
+
+**If user selects a non-English language, ask:**
+
+```
+AskUserQuestion: What should be translated?
+
+Options:
+1. Communication only — AI responds in selected language, artifacts in English
+2. Communication and artifacts — Both AI responses and generated files in selected language
+3. Artifacts only — AI responds in English, generates files in selected language
+```
+
+**Git workflow detection (if `config.yaml` is missing or the `git:` section is incomplete):**
+
+1. Check whether the project uses git:
+   - If `.git` exists - set `git.enabled: true`
+   - If `.git` does not exist - set `git.enabled: false` and `git.create_branches: false`
+2. If git is enabled, detect the default/base branch from git metadata:
+   - Prefer `origin/HEAD`
+   - Fallback to remote metadata (`git remote show origin`)
+   - Fallback to `main`
+3. If git is enabled, ask whether `/aif-plan full` should create a new branch:
+
+```
+AskUserQuestion: How should full plans behave in git?
+
+Options:
+1. Create a new branch (Recommended) - /aif-plan full creates a branch and saves the full plan as a branch-scoped file
+2. Stay on the current branch - /aif-plan full still creates a rich full plan, but without creating a new branch
+```
+
+**Store resolved settings in `.ai-factory/config.yaml`:**
+
+- Use `skills/aif/references/config-template.yaml` as the source template.
+- Preserve the inline comments so developers can edit `config.yaml` manually later.
+- Fill in the resolved values; do **not** replace the file with a stripped-down minimal YAML blob.
+
+```yaml
+language:
+  ui: <resolved-ui-language>
+  artifacts: <resolved-artifacts-language>
+  technical_terms: keep
+
+paths:
+  description: .ai-factory/DESCRIPTION.md
+  architecture: .ai-factory/ARCHITECTURE.md
+  docs: docs/
+  roadmap: .ai-factory/ROADMAP.md
+  research: .ai-factory/RESEARCH.md
+  rules_file: .ai-factory/RULES.md
+  plan: .ai-factory/PLAN.md
+  plans: .ai-factory/plans/
+  fix_plan: .ai-factory/FIX_PLAN.md
+  security: .ai-factory/SECURITY.md
+  references: .ai-factory/references/
+  patches: .ai-factory/patches/
+  evolutions: .ai-factory/evolutions/
+  evolution: .ai-factory/evolution/
+  specs: .ai-factory/specs/
+  rules: .ai-factory/rules/
+
+workflow:
+  auto_create_dirs: true
+  plan_id_format: slug
+  analyze_updates_architecture: true
+  architecture_updates_roadmap: true
+  verify_mode: normal
+
+git:
+  enabled: <true-if-git-detected-else-false>
+  base_branch: <detected-base-branch-or-main>
+  create_branches: <true-or-false-based-on-user-choice>
+  branch_prefix: feature/
+  skip_push_after_commit: false
+
+rules:
+  base: .ai-factory/rules/base.md
+```
+
+**Create `.ai-factory/rules/base.md` from codebase evidence:**
+
+After language resolution, analyze the codebase to detect:
+- Naming conventions (camelCase, snake_case, PascalCase)
+- Module boundaries (src/core/, src/cli/, src/utils/)
+- Error handling patterns (try/catch, error codes)
+- Logging patterns (console.log, winston, pino)
+- Test patterns (jest, mocha, vitest)
+
+Create `.ai-factory/rules/base.md` with detected conventions:
+
+```markdown
+# Project Base Rules
+
+> Auto-detected conventions from codebase analysis. Edit as needed.
+
+## Naming Conventions
+
+- Files: [detected pattern]
+- Variables: [detected pattern]
+- Functions: [detected pattern]
+- Classes: [detected pattern]
+
+## Module Structure
+
+- [detected module boundaries]
+
+## Error Handling
+
+- [detected error handling pattern]
+
+## Logging
+
+- [detected logging pattern]
+```
+
+---
+
 ### Mode 1: Analyze Existing Project
 
 **Trigger:** `/aif` (no arguments) + project has config files
@@ -139,6 +278,10 @@ Based on analysis, create project specification:
 - Identified patterns
 - Architecture notes
 
+**Step 2.5: Language Resolution**
+
+After creating DESCRIPTION.md, resolve language settings (see [Language Resolution](#language-resolution)).
+
 **Step 3: Recommend Skills & MCP**
 
 | Detection | Skills | MCP |
@@ -180,7 +323,11 @@ Proceed? [Y/n]
 
 1. Create directory: `mkdir -p .ai-factory`
 2. Save `.ai-factory/DESCRIPTION.md`
-3. For each external skill from skills.sh:
+3. **Create config.yaml and rules/base.md** (from language resolution step):
+   - Ensure `.ai-factory/rules/` directory exists
+   - Write `.ai-factory/config.yaml` from `skills/aif/references/config-template.yaml`, preserving comments and filling in the resolved values
+   - Write `.ai-factory/rules/base.md` with detected conventions
+4. For each external skill from skills.sh:
    ```bash
    npx skills install {{skills_cli_agent_flag}} <name>
    # AUTO-SCAN: immediately after install
@@ -189,10 +336,10 @@ Proceed? [Y/n]
    - Exit 1 (BLOCKED) → `rm -rf <path>`, warn user, skip this skill
    - Exit 2 (WARNINGS) → show to user, ask confirmation
    - Exit 0 (CLEAN) → read files yourself (Level 2), verify intent, proceed
-4. Generate custom skills via `/aif-skill-generator` (pass URLs for Learn Mode when docs are available)
-5. Configure MCP in `{{settings_file}}`
-6. Generate `AGENTS.md` in project root (see [AGENTS.md Generation](#agentsmd-generation))
-7. Generate architecture document via `/aif-architecture` (see [Architecture Generation](#architecture-generation))
+5. Generate custom skills via `/aif-skill-generator` (pass URLs for Learn Mode when docs are available)
+6. Configure MCP in `{{settings_file}}`
+7. Generate `AGENTS.md` in project root (see [AGENTS.md Generation](#agentsmd-generation))
+8. Generate architecture document via `/aif-architecture` (see [Architecture Generation](#architecture-generation))
 
 ---
 
@@ -252,6 +399,10 @@ Save to `.ai-factory/DESCRIPTION.md`.
 mkdir -p .ai-factory
 ```
 
+**Step 2.5: Language Resolution**
+
+After creating DESCRIPTION.md, resolve language settings (see [Language Resolution](#language-resolution)).
+
 **Step 3: Search & Install Skills**
 
 Based on confirmed stack:
@@ -292,6 +443,10 @@ After getting description, proceed with same stack selection as Mode 2:
 
 Same as Mode 2.
 
+**Step 3.5: Language Resolution**
+
+After creating DESCRIPTION.md, resolve language settings (see [Language Resolution](#language-resolution)).
+
 **Step 4: Setup Context**
 
 Install skills, configure MCP, generate `AGENTS.md`, and generate architecture document via `/aif-architecture` as in Mode 1.
@@ -406,8 +561,8 @@ Install skills, configure MCP, generate `AGENTS.md`, and generate architecture d
 
 ## Agent Rules
 - Never combine shell commands with `&&`, `||`, or `;` — execute each command as a separate Bash tool call. This applies even when a skill, plan, or instruction provides a combined command — always decompose it into individual calls.
-  - ❌ Wrong: `git checkout main && git pull`
-  - ✅ Right: Two separate Bash tool calls — first `git checkout main`, then `git pull`
+  - ❌ Wrong: `git checkout <configured-base-branch> && git pull`
+  - ✅ Right: Two separate Bash tool calls — first `git checkout <configured-base-branch>`, then `git pull origin <configured-base-branch>`
 ```
 
 **Rules for AGENTS.md:**
@@ -430,7 +585,7 @@ Install skills, configure MCP, generate `AGENTS.md`, and generate architecture d
 
 - Primary ownership in this command: `.ai-factory/DESCRIPTION.md`, setup-time `AGENTS.md`, installed skills, and MCP configuration.
 - Delegated ownership: invoke `/aif-architecture` to create/update `.ai-factory/ARCHITECTURE.md`.
-- Read-only context in this command by default: `.ai-factory/ROADMAP.md`, `.ai-factory/RULES.md`, `.ai-factory/RESEARCH.md`, and plan files.
+- Read-only context in this command by default: the resolved roadmap, RULES.md, research, and plan artifacts.
 
 ## CRITICAL: Do NOT Implement
 
@@ -455,7 +610,7 @@ MCP configured: [list]
 
 To start development:
 - /aif-roadmap — Create a strategic roadmap with milestones (recommended for new projects)
-- /aif-plan <description> — Plan implementation (creates branch + plan, or quick plan)
+- /aif-plan <description> — Plan implementation (fast plan or full plan with optional branch/worktree flow)
 - /aif-implement — Execute existing plan
 
 Ready when you are!

package/skills/aif/references/config-template.yaml

@@ -0,0 +1,190 @@
+# AI Factory Configuration
+# This file configures AI Factory behavior for your project.
+# All sections are optional — defaults are used when not specified.
+
+# =============================================================================
+# Language Settings
+# =============================================================================
+# Controls the language used in AI-generated content and communication.
+
+language:
+  # Language for AI-agent communication (prompts, questions, explanations)
+  # Options: en, ru, de, fr, es, zh, ja, ko, pt, it
+  # Default: en
+  ui: en
+
+  # Language for generated artifacts (plans, specs, documentation)
+  # Options: en, ru, de, fr, es, zh, ja, ko, pt, it
+  # Default: en (same as ui if not specified)
+  artifacts: en
+
+  # How to handle technical terms in translations
+  # Options:
+  #   - keep: preserve original English terms (API, database, etc.)
+  #   - translate: translate where common translation exists
+  # Default: keep
+  technical_terms: keep
+
+# =============================================================================
+# Path Configuration
+# =============================================================================
+# Custom paths for AI Factory artifacts.
+# All paths are relative to project root.
+
+paths:
+  # Project description file
+  # Default: .ai-factory/DESCRIPTION.md
+  description: .ai-factory/DESCRIPTION.md
+
+  # Architecture guidelines file
+  # Default: .ai-factory/ARCHITECTURE.md
+  architecture: .ai-factory/ARCHITECTURE.md
+
+  # Detailed documentation directory used by /aif-docs
+  # README.md remains the landing page in the project root.
+  # Change this if you want docs pages under another folder like
+  # documentation/, handbook/, or site/docs/.
+  # Default: docs/
+  docs: docs/
+
+  # Roadmap file
+  # Default: .ai-factory/ROADMAP.md
+  roadmap: .ai-factory/ROADMAP.md
+
+  # Research notes file
+  # Default: .ai-factory/RESEARCH.md
+  research: .ai-factory/RESEARCH.md
+
+  # Top-level project rules file (axioms)
+  # Default: .ai-factory/RULES.md
+  rules_file: .ai-factory/RULES.md
+
+  # Fast-mode plan file
+  # Used by /aif-plan fast for a single quick plan.
+  # Keep this separate from paths.plans unless you want fast plans
+  # to live next to full named plans.
+  # Default: .ai-factory/PLAN.md
+  plan: .ai-factory/PLAN.md
+
+  # Full-mode plans directory
+  # /aif-plan full stores named plan files here.
+  # In git-aware mode this is typically branch-scoped.
+  # In no-git mode it stores slug-based plan files.
+  # Default: .ai-factory/plans/
+  plans: .ai-factory/plans/
+
+  # Fix plan file
+  # Default: .ai-factory/FIX_PLAN.md
+  fix_plan: .ai-factory/FIX_PLAN.md
+
+  # Security ignore-state file
+  # Default: .ai-factory/SECURITY.md
+  security: .ai-factory/SECURITY.md
+
+  # Knowledge references directory
+  # Default: .ai-factory/references/
+  references: .ai-factory/references/
+
+  # Self-improvement patches directory
+  # Default: .ai-factory/patches/
+  patches: .ai-factory/patches/
+
+  # Evolution logs directory
+  # Default: .ai-factory/evolutions/
+  evolutions: .ai-factory/evolutions/
+
+  # Reflex loop state directory
+  # Default: .ai-factory/evolution/
+  evolution: .ai-factory/evolution/
+
+  # Specs directory (archived plans)
+  # Default: .ai-factory/specs/
+  specs: .ai-factory/specs/
+
+  # Rules directory
+  # Default: .ai-factory/rules/
+  rules: .ai-factory/rules/
+
+# =============================================================================
+# Workflow Settings
+# =============================================================================
+# Controls AI Factory workflow behavior.
+
+workflow:
+  # Automatically create .ai-factory/ directories when missing
+  # Default: true
+  auto_create_dirs: true
+
+  # Plan ID format for new plans
+  # Options: slug, timestamp, uuid
+  # Default: slug (derived from branch or task description)
+  plan_id_format: slug
+
+  # Whether the setup/analyze flow updates ARCHITECTURE.md
+  # Default: true
+  analyze_updates_architecture: true
+
+  # Whether /aif-architecture updates ROADMAP.md
+  # Default: true
+  architecture_updates_roadmap: true
+
+  # Default verification mode
+  # Options: strict, normal, lenient
+  # Default: normal
+  verify_mode: normal
+
+# =============================================================================
+# Git Settings
+# =============================================================================
+
+git:
+  # Whether this project uses git-aware workflows
+  # If false:
+  #   - /aif-plan full does not create branches
+  #   - /aif-review and /aif-verify do not assume a base branch exists
+  #   - merge/push guidance is skipped
+  # Default: auto-detected from the repository (.git presence)
+  enabled: true
+
+  # Default branch for diff/review/merge targets
+  # Examples: main, master, develop, trunk, 2.x
+  # Default: auto-detected from git metadata, fallback main
+  base_branch: main
+
+  # Automatically create feature branches for plans
+  # Applies only when git.enabled = true
+  # If false, /aif-plan full still creates a full plan but stays on the
+  # current branch (or uses a slug-named full plan in no-git mode)
+  # Default: true when git is enabled
+  create_branches: true
+
+  # Branch name prefix for new features
+  # Applies only when create_branches = true
+  # Default: feature/
+  branch_prefix: feature/
+
+  # Skip push prompt after /aif-commit creates a commit
+  # If true:
+  #   - /aif-commit ends after successful local commit
+  #   - no "Push to remote?" prompt is shown
+  # Default: false
+  skip_push_after_commit: false
+
+# =============================================================================
+# Rules Configuration
+# =============================================================================
+# Configure the rules hierarchy for this project.
+
+rules:
+  # Base rules file (project-specific conventions)
+  # This file is created by /aif during project setup
+  # Default: .ai-factory/rules/base.md
+  base: .ai-factory/rules/base.md
+
+  # Area-specific rules files
+  # These are created by /aif-rules when you add area-specific conventions
+  # Uncomment and add paths as needed:
+  # api: .ai-factory/rules/api.md
+  # frontend: .ai-factory/rules/frontend.md
+  # backend: .ai-factory/rules/backend.md
+  # database: .ai-factory/rules/database.md

package/skills/aif-architecture/SKILL.md

@@ -12,9 +12,18 @@ Generate `.ai-factory/ARCHITECTURE.md` with architecture decisions tailored to t
 
 ## Workflow
 
-### Step 0: Load Project Context
+### Step 0: Load Config & Project Context
 
-**Read `.ai-factory/DESCRIPTION.md`** if it exists to understand:
+**FIRST:** Read `.ai-factory/config.yaml` if it exists to resolve:
+- **Paths:** `paths.description` and `paths.architecture`
+- **Language:** `language.ui` for prompts and `language.artifacts` for generated architecture content
+
+If config.yaml doesn't exist, use defaults:
+- DESCRIPTION.md: `.ai-factory/DESCRIPTION.md`
+- ARCHITECTURE.md: `.ai-factory/ARCHITECTURE.md`
+- Language: `en` (English)
+
+**THEN:** Read `.ai-factory/DESCRIPTION.md` (use path from config) if it exists to understand:
 - Tech stack (language, framework, database, ORM)
 - Project size and complexity
 - Core features and requirements
@@ -85,13 +94,11 @@ Architecture options:
 - **Modular Monolith** — single deployment with strong module boundaries, good default for most projects
 - **Layered Architecture** — simple layers (presentation → business → data), good for smaller projects
 
-### Step 2: Generate .ai-factory/ARCHITECTURE.md
+### Step 2: Generate the Architecture Artifact
 
-```bash
-mkdir -p .ai-factory
-```
+Create the parent directory for the resolved architecture path if needed.
 
-Generate `.ai-factory/ARCHITECTURE.md` with the following structure, **adapted to the project's tech stack and language**:
+Generate the resolved architecture artifact (default: `.ai-factory/ARCHITECTURE.md`) with the following structure, **adapted to the project's tech stack and language**:
 
 ```markdown
 # Architecture: [Pattern Name]
@@ -151,11 +158,11 @@ Generate `.ai-factory/ARCHITECTURE.md` with the following structure, **adapted t
 
 ### Step 3: Update DESCRIPTION.md
 
-If `.ai-factory/DESCRIPTION.md` exists, add an `## Architecture` section (or update if it already exists):
+If the resolved DESCRIPTION.md path exists, add an `## Architecture` section (or update if it already exists):
 
 ```markdown
 ## Architecture
-See `.ai-factory/ARCHITECTURE.md` for detailed architecture guidelines.
+See the configured architecture artifact for detailed architecture guidelines.
 Pattern: [chosen pattern name]
 ```
 
@@ -188,6 +195,7 @@ All workflow skills (/aif-plan, /aif-implement) will now follow these architectu
 ## Artifact Ownership
 
 - Primary ownership: `.ai-factory/ARCHITECTURE.md`.
+- Respect config overrides: write to the resolved architecture path from `config.yaml` when provided.
 - Allowed companion updates: architecture pointer in `.ai-factory/DESCRIPTION.md`, architecture row in `AGENTS.md` context table.
 - Read-only context: roadmap, rules, research, and plan artifacts unless user explicitly requests otherwise.
 

package/skills/aif-best-practices/SKILL.md

@@ -274,3 +274,9 @@ or using optional chaining: `user?.profile?.name`"
 | Errors | Specific types, never swallow, log context |
 | Tests | AAA pattern, test behavior, descriptive names |
 | Reviews | Be specific, suggest solutions, be kind |
+
+## Artifact Ownership and Config Policy
+
+- Primary ownership: none. This skill is advisory and reference-only.
+- Write policy: do not create or modify project artifacts by default.
+- Config policy: config-agnostic by design. Follow repository context, `.ai-factory/ARCHITECTURE.md`, and skill-context overrides instead of reading `config.yaml`.

package/skills/aif-build-automation/SKILL.md

@@ -498,3 +498,9 @@ After writing the build file, integrate quick commands into project docs.
 For detailed integration procedures (README, AGENTS.md, existing markdown) → read `references/DOC-INTEGRATION.md`
 
 Brief: scan for existing command sections, update or append quick reference, suggest AGENTS.md creation if missing.
+
+## Artifact Ownership and Config Policy
+
+- Primary ownership: generated or enhanced build automation files (`Makefile`, `Taskfile.yml`, `justfile`, `magefile.go`).
+- Allowed companion updates: quick command snippets in existing docs or `AGENTS.md` when directly tied to the generated build workflow.
+- Config policy: config-agnostic by design. This skill uses repository detection and fixed AI Factory context files rather than `config.yaml`.

package/skills/aif-ci/SKILL.md

@@ -498,3 +498,9 @@ Display summary using format from `references/AUDIT-REPORT.md` (Summary Display
 ### 7.2 Suggest Follow-Up Skills
 
 Suggest: `/aif-build-automation` for CI targets in Makefile/Taskfile, `/aif-dockerize` for containerization.
+
+## Artifact Ownership and Config Policy
+
+- Primary ownership: CI pipeline artifacts such as `.github/workflows/*` and `.gitlab-ci.yml`.
+- Allowed companion updates: none by default outside CI files.
+- Config policy: config-agnostic by design. This skill relies on repository detection and explicit user choices, not `config.yaml`.

package/skills/aif-commit/SKILL.md

@@ -12,6 +12,17 @@ Generate commit messages following the [Conventional Commits](https://www.conven
 
 ## Workflow
 
+**FIRST:** Read `.ai-factory/config.yaml` if it exists to resolve:
+- **Paths:** `paths.description`, `paths.architecture`, `paths.rules_file`, `paths.roadmap`, and `paths.rules`
+- **Language:** `language.ui` for prompts and commit message conventions
+- **Git preference:** `git.skip_push_after_commit` for post-commit push behavior
+- **Rules hierarchy:** `rules.base` plus any named `rules.<area>` entries
+
+If config.yaml doesn't exist, use defaults:
+- Paths: `.ai-factory/` for all artifacts
+- Language: `en` (English)
+- Git preference: `skip_push_after_commit: false`
+
 **Read `.ai-factory/skill-context/aif-commit/SKILL.md`** — MANDATORY if the file exists.
 
 This file contains project-specific rules accumulated by `/aif-evolve` from patches,
@@ -38,8 +49,9 @@ If any rule is violated — fix the output before presenting it to the user.
    - If nothing staged, show warning and suggest staging
 
 2. **Run Context Gates (Read-Only)**
-   - Check `.ai-factory/ARCHITECTURE.md` and `.ai-factory/DESCRIPTION.md` (if present) to catch obvious scope/boundary drift
-   - Check `.ai-factory/RULES.md` and `.ai-factory/ROADMAP.md` (if present) to catch rule and milestone alignment issues
+   - Check the resolved architecture and description artifacts (use paths from config) to catch obvious scope/boundary drift
+   - Check the resolved RULES.md and roadmap artifacts (use paths from config) to catch rule and milestone alignment issues
+   - Check rules hierarchy (resolved `paths.rules_file` + `rules.base` + named `rules.<area>`) for commit conventions
    - Missing optional files (`ROADMAP.md`, `RULES.md`) are `WARN`, not blockers
    - Never modify context artifacts from this command
 
@@ -128,23 +140,27 @@ When invoked:
    - **Cancel** → stop, do NOT commit. End the workflow
 
 8. Execute `git commit` with the confirmed message
-9. After a successful commit, offer to push:
-   - Show branch/ahead status: `git status -sb`
-   - If the branch has no upstream, use: `git push -u origin <branch>`
-   - Otherwise: `git push`
+9. Post-commit push handling:
+   - If `git.skip_push_after_commit = true` in resolved config:
+     - Skip push prompt entirely
+     - End workflow after successful local commit
+   - Otherwise (default behavior), offer to push:
+     - Show branch/ahead status: `git status -sb`
+     - If the branch has no upstream, use: `git push -u origin <branch>`
+     - Otherwise: `git push`
 
-   ```
-   AskUserQuestion: Push to remote?
+     ```
+     AskUserQuestion: Push to remote?
 
-   Options:
-   1. Push now
-   2. Skip push
-   ```
+     Options:
+     1. Push now
+     2. Skip push
+     ```
 
-   - **Push now** → execute push command based on upstream status:
-     - if branch has no upstream → `git push -u origin <branch>`
-     - otherwise → `git push`
-   - **Skip push** → end the workflow
+     - **Push now** → execute push command based on upstream status:
+       - if branch has no upstream → `git push -u origin <branch>`
+       - otherwise → `git push`
+     - **Skip push** → end the workflow
 
 If argument provided (e.g., `/aif-commit auth`):
 - Use it as the scope
@@ -155,7 +171,7 @@ If argument provided (e.g., `/aif-commit auth`):
 - Never commit secrets or credentials
 - Review large diffs carefully before committing
 - `/aif-commit` has no implicit strict mode — context gates are warning-first unless user explicitly requests blocking behavior
-- Treat `.ai-factory/ARCHITECTURE.md`, `.ai-factory/ROADMAP.md`, `.ai-factory/RULES.md`, and `.ai-factory/DESCRIPTION.md` as read-only context in this command
+- Treat the resolved architecture, roadmap, RULES.md, and description artifacts as read-only context in this command
 - If staged changes contain unrelated work (e.g., a feature + a bugfix, or changes to independent modules), suggest splitting into separate commits:
   1. Show which files/hunks belong to which commit
   2. Confirm split plan with the user:

package/skills/aif-dockerize/SKILL.md

@@ -517,3 +517,9 @@ Templates: `templates/deploy.sh`, `templates/update.sh`, `templates/logs.sh`, `t
 Display a summary of all created/updated files using the format from `references/SUMMARY-FORMAT.md`.
 
 Suggest follow-up: `/aif-build-automation` for Docker targets, `/aif-docs` for documentation.
+
+## Artifact Ownership and Config Policy
+
+- Primary ownership: Docker artifacts (`Dockerfile`, `compose*.yml`, `.dockerignore`, `docker/*`, `deploy/scripts/*`, and related `.env.example` scaffolding when created by this skill).
+- Allowed companion updates: none outside Docker and deployment artifacts by default.
+- Config policy: config-agnostic by design. This skill uses repository detection, explicit infrastructure choices, and fixed AI Factory context files rather than `config.yaml`.