datalad-configuration

To set DataLad configuration at the dataset scope, this Skill applies get, set, or unset actions to dataset-scoped keys like annex.backend, ensuring changes target the dataset rather than the global user environment. It also advises committing dataset changes when using this scope.

Managing git config keys for a DataLad dataset requires a dataset-aware wrapper that validates the DataLad context before execution. This Skill safely reads and writes DataLad-specific keys like datalad.* and annex.* while avoiding direct git config edits that bypass DataLad rules.

Yes, you can change annex.backend for an individual clone without affecting global Git configuration. This Skill explicitly supports clone-local scope selection, ensuring configuration changes remain isolated to the specific clone and do not alter user-level settings.

Yes, this Skill validates the DataLad context before modifying git config. It ensures actions follow get, set, or unset operations with explicit scope selection, and it prints the full command prior to running to maintain transparency during configuration changes.

You should avoid direct git config for datalad.* and annex.* keys because manual global edits can bypass DataLad rules. This Skill provides a safe wrapper that respects DataLad-specific keys and applies changes to the appropriate dataset, local, or global scope.

Available scopes for setting DataLad configuration include dataset-scoped, clone-local, and global user-level Git configuration. This Skill ensures explicit scope selection for actions like get, set, and unset to manage keys like annex.backend and user.name in the correct context.