fraujulian/MyAiConfiguration
1
0 Fork 0
Code Issues Pull Requests Actions Activity

docs: reorganize configuration guides
CI / Capabilities and shell quality (push) Successful in 21s
Details
CI / Python tests and compilation (push) Failing after 35s
Details
CI / Build and inspect generated packages (push) Skipped
Details
CI / Bash integration and installation guards (push) Skipped
Details
CI / Installed client configuration smoke tests (push) Skipped
Details
CI / Qwen retrieval integration (push) Skipped
Details
CI / PowerShell tests on Ubuntu (push) Failing after 14s
Details
CI / CI configuration security checks (push) Successful in 4s
Details

Browse Source
This commit is contained in:
fraujulian committed 2026-09-18 11:38:30 +02:00
1 parent 145169dea8
commit 023d1610ba
5 files changed
+145 -135
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

AI-Instructions.md
+3 -3
View File
@@ -36,8 +36,8 @@ Write all repository content, generated instructions, scripts, prompts, document
## Workflow
- Choose the smallest sufficient verification based on the change's behavior, affected consumers, risk, and remaining uncertainty. Inspection may suffice for low-risk changes; full builds, test suites, and independent reviews are not automatic.
- Run `scripts/build.ps1 -Summary` to regenerate packages when shared definitions, adapters, or generation logic change. This generates configuration packages; it does not require building applications that use them.
- Run `scripts/doctor.ps1 -Summary` when installation, client configuration, hooks, or environment changes need its checks. Changes to instruction wording alone do not require it.
- Run `scripts/commands/build.ps1 -Summary` to regenerate packages when shared definitions, adapters, or generation logic change. This generates configuration packages; it does not require building applications that use them.
- Run `scripts/commands/doctor.ps1 -Summary` when installation, client configuration, hooks, or environment changes need its checks. Changes to instruction wording alone do not require it.
- Run focused script tests when script behavior changes. Broaden or repeat checks only when failures, affected dependencies, or unresolved risks justify it.
- Preserve backward compatibility where practical.
- Keep changes focused on the requested configuration behavior.
@@ -52,7 +52,7 @@ Write all repository content, generated instructions, scripts, prompts, document
## Installation and security
- Do not install global configuration automatically.
- Perform global installation only after explicit user instruction, using `scripts/install.ps1` so replaced managed files are backed up.
- Perform global installation only after explicit user instruction, using `scripts/commands/install.ps1` so replaced managed files are backed up.
- Do not add project-specific rules, secrets, credentials, authentication state, or generated runtime state.
## Version control