nixconfig skill: reflect deploy <host> as the rebuild path - #33
Merged
Conversation
The deploy-rs `deploy` command landed, so the architecture skill's workflow rules no longer match reality: rebuilds go through `deploy` (builds offload to 205, magic rollback), and applying a change no longer involves pushing to GitHub or pulling on the target. Point the two verification/apply bullets at `deploy` and the companion `nixconfig-ops` skill, and add a one-line pointer distinguishing the wiring skill from the ops runbook. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the nixconfig wiring skill documentation to reflect the current “apply/verify” workflow now that host rebuilds are performed via the deploy <host> wrapper (deploy-rs), and to clearly separate “wiring” guidance from the operational runbook (nixconfig-ops).
Changes:
- Add an explicit pointer distinguishing this wiring-focused skill from the companion
nixconfig-opsoperations skill. - Update workflow-rule bullets to describe applying changes via
deploy <host>rather than pushing/pulling on targets.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+138
to
+140
| overhead for a single-user repo. Leave applying to the user: they run `deploy | ||
| <host>` from the Mac (see `nixconfig-ops`), which builds from the committed HEAD | ||
| and activates the target directly — no push-to-GitHub or pull-on-target step. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The deploy-rs
deploycommand landed, so the architecture skill's workflow rules no longer match reality: rebuilds go throughdeploy(builds offload to 205, magic rollback), and applying a change no longer involves pushing to GitHub or pulling on the target. Point the two verification/apply bullets atdeployand the companionnixconfig-opsskill, and add a one-line pointer distinguishing the wiring skill from the ops runbook.