1.7 KiB
1.7 KiB
name, description, version
| name | description | version |
|---|---|---|
| nixos-workflow | STRICT workflow for managing Pi assets via Gitea on NixOS | 1.1.0 |
NixOS Gitea Asset Manager (STRICT)
You are an expert at managing Pi Agent assets on a NixOS system using a Gitea-centric workflow.
⛔ CRITICAL PROHIBITIONS
- NEVER suggest or perform edits to
home.nixto add individual extensions or skills. - NEVER use
pi installornpm install -g(Nix store is read-only).
🛠 THE SOURCE OF TRUTH
All assets MUST be managed in the local Git-controlled directory:
- Local Path:
/home/sam/.agents - Remote URL:
https://gitea.lab.audasmedia.com.au/sam/pi-config
🏗 ASSET DEPLOYMENT WORKFLOW
When the user asks for a new tool or skill, you MUST follow these steps exactly:
- Local Authoring:
- Write code/markdown directly into the appropriate subfolder in
~/.agents/(e.g.,extensions/orskills/). - If cloning an external repo, immediately
rm -rf .gitinside that folder to prevent submodule issues. Also inside that folder remove '.gitignore' if it is there.
- Write code/markdown directly into the appropriate subfolder in
- Local Dependency Check:
- If an extension, run
npm installinside that specific subfolder.
- If an extension, run
- Gitea Synchronization:
cd /home/sam/.agentsgit add .git commit -m "Add [asset name]"git push origin main
- Project Activation:
- Instruct the user to add the relative path (e.g.,
"extensions/my-tool/index.ts") to their current project's.pi/settings.json.
- Instruct the user to add the relative path (e.g.,
❄ NIXOS INTEGRATION
The ONLY time you reference Nix is for the Global Settings. Confirm the user's home.nix contains a settings.json that points to the Gitea source:
"source": "git:https://gitea.lab.audasmedia.com.au/sam/pi-config"