workspace-import
/workspace-import
Pilnuje reguł ignorowania i importu do repozytorium, by pakowanie, dane logowania i dane klientów nie trafiły do historii.
- Autor
- DariuszDusza ↗
- Repozytorium
- agentic-workflow-foundry ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 06.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 06.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Pilnuje reguł ignorowania i importu do repozytorium, by pakowanie, dane logowania i dane klientów nie trafiły do historii.
Oryginalny opis (EN)
Use when changing the ignore rules that decide what may enter history (any .gitignore, a new credential or packaging class, a question about what git add would stage), or when copying another project tree into this repository. Keeps packaging, credentials and customer data out of a history that cannot forget.
Jak działa
- Required context
- The facts behind every rule here
- The ignore rules: the everyday case
- An import: the rare case
- Verify
- Escalate when
Podgląd SKILL.md
--- name: workspace-import description: Use when changing the ignore rules that decide what may enter history (any .gitignore, a new credential or packaging class, a question about what git add would stage), or when copying another project tree into this repository. Keeps packaging, credentials and customer data out of a history that cannot forget. --- # Workspace import, and the ignore rules that make it safe ## Required context 1. `.agents/guardrails/repo-hygiene.md`: what may enter history, and why. 2. `.agents/guardrails/imports.md`: the import procedure. 3. `.agents/guardrails/git-safety.md`: version identity and tags. 4. `.agents/rules/gitignore-anchoring.md`: applies with every ignore file. 5. `.agents/rules/areas-manifest.md`: an imported tree becomes a declared area. ## The facts behind every rule here A commit object keeps what it is given, and `git rm` does not remove a file from history. An imported project typically carries far more packaging than content (dependency directories, build output, caches, uploaded media), and often a credential file or two. Getting the ignore rules wrong once is permanent unless history is rewritten, which is its own escalation. ## The ignore rules: the everyday case - **Assert both directions.** After any ignore-file edit, the assertions must say what must be ignored **and** the neighbouring file that must stay tracked. A rule without an assertion is a rule nobody will notice breaking (`docs/decisions/0005-every-gate-has-an-assertion-suite.md`). - **Anchoring**: a slash anywhere but the end anchors the pattern to its own file's directory. Use `**/` for a pattern meant to match at any depth. - **Negations need the parent included.** Git cannot re-include a file whose parent directory is excluded; exclude the directory's contents, then negate the keeper. - **New credential classes go in the root ignore file**, never only a sub-project's. - **Do not rely on a personal global excludes file.** It does not travel to another machine, a container or CI. - `tools/preflight-init.sh` is read-only: it reports what `git add` would stage and refuses on credential shapes. Gigabytes in its report means an exclude failed. ## An import: the rare case **Escalate first.** An import is high-risk. Confirm with the operator in the current conversation before starting; an approval never carries forward from a previous import. The order, never reordered: 1. Ignore-rule assertions green **before** anything is copied. 2. Copy with an explicit exclude list (for example `rsync` with excludes). Never a bare recursive copy of everything. Keep the imported tree's own ignore files: they are additional layers. 3. `tools/preflight-init.sh`: the staged size should match the content you expect, not the packaging. Gigabytes means an exclude failed: fix the rules and re-run. 4. Assertions again, then `tools/check-areas.sh`. 5. Declare the area in `.agents/areas.json`, add its node to `knowledge-graph/workspace.jsonld`, commit. Never commit intending to clean up afterwards: the cleanup cannot reach history. **Tags are repository-global.** A `git describe --match` glob searches the whole repository. An imported product's tags can outrank another product's release and silently become its version. Namespace tags per product, and never create a tag as a side effect of an import. **Hand off.** An imported tree may carry its own agent guidance. It stays authoritative inside that tree; this repository's guidance points at it rather than restating it. ## Verify ```bash tools/preflight-init.sh # what would be staged; refuses on credential shapes tools/check-secrets.sh tools/check-areas.sh make test-gates # includes the preflight tool's own suite ``` Reviewer: `repo-hygiene-reviewer`; `security-data-reviewer` when credentials are involved. ## Escalate when - Any import, before it starts. - Anything already committed needs removing from history. - A tag would be created, moved or deleted. - The preflight report is far larger than the content you meant to add.
Wersje
W bazie nie ma innych skilli o nazwie workspace-import.
Migawka bazy z 13.11.2026 · wersja paczki 46e2d041166f (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90git-history-secret-audit
Sprawdza całą historię repozytorium git pod kątem sekretów, także w nieosiągalnych obiektach i regułach ignorowania. - 95keeping-git-repos-clean
Zapobiega commitowaniu sekretów i zbędnych plików, wykrywa je w repozytorium Git, usuwa z historii i pomaga rotować dane dostępowe. - 100secret-scanner
Wykrywa zakodowane na sztywno dane logowania w drzewie plików i historii gita, a potem prowadzi rotację i czyszczenie historii. - 100secret-guard
Sprawdza pliki konfiguracyjne i zmiany przed zapisaniem lub wysłaniem, by klucze i tokeny nie trafiły do repozytorium. - 100migrate-internal-package
Przenosi pakiet z innego repozytorium TryGhost do Ghost jako wewnętrzny pakiet workspace z zachowaniem historii Git, wraz z PR importu historii i usunięciem źródła. - 100python-packaging-security-audit
Ocenia bezpieczeństwo repozytorium pakietu Python, łącząc równolegle analizę statyczną, skanowanie binariów i inspekcję historii git w jeden raport z oceną ryzyka.