Skip to content

Which low-friction checkable dotfiles rules should become hooks or permission rules? #15665

Closed

Description

@kyle-sexton

Question

Which low-friction checkable rules in the dotfiles user instructions should become hooks or permission rules?

From the talk

Chapter 3, slides 12 and 23: every correction becomes a check.

Today and the gap

Of 107 rule units in the always-loaded user instructions, 15 are checkable and prose-only, 13 are already enforced, and 75 are judgment. Candidates: edit the chezmoi source, not the rendered file; no per-repository plugin pin; the repository sync command, not a hand loop; no worktree or clone in a temp directory; literal GitHub write commands; files rendered by provisioning.

Recommendation

Convert them (menu priority P1, full slice), each through /corrections:codify with a proven check. Basis: the counts above. Declined already: a global deny on VAR=value, export and redirects, and a provenance-note lint (high friction or false positives).

Alternatives

Convert a subset by how often each is broken; keep them as prose.

Done would add

Decided here, built in the dotfiles repository: hooks or permission rules, each replacing its prose line.

Activity

  1. added
    wayfind: interviewWayfind decision item: contract/requirements call the user must make; human in the loop.
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Nov 12, 2026
  2. added theissue type on Nov 12, 2026
  3. github-actions commented on Nov 12, 2026

    @github-actions
    Contributor

    Size: Medium
    Complexity: Medium
    Uncertainty: Knowable
    Flags: intent
    Blocked by: none

    I understood this as an open scope decision. Of 15 checkable, prose-only dotfiles rules, which become hooks or permission rules, each added through /corrections:codify with a proven check? The work itself would land in the dotfiles repository. I found no recorded decision and no merged pull request that covers it.

    1. Which scope should be built?
      RECOMMENDED: convert all 15 checkable rules (the P1 full slice), keeping the declined items (a global deny on VAR=value, export and redirects, and a provenance-note lint) out. Basis: the issue's own counts and recommendation. Only low-friction checks remain, so a break-frequency subset adds little. Keeping them as prose leaves the 15 rules unenforced.

    To answer, post a comment that starts with this line:

    **Decision recorded.** <your answer>
    

    Automated triage. A maintainer reviews it.

  4. added
    needs-owner-decisionAwaiting a human or maintainer judgment call.
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 12, 2026
  5. kyle-sexton commented on Nov 13, 2026

    @kyle-sexton
    MemberAuthor

    Resolved (owner, 2026-11-13: "go w/ recommendations", to the question restated in full with its permission changes): fix the stale prose first, then convert the low-friction rules that have evidence, each through /corrections:codify and placed by scope. Not all of the roughly 16 unenforced checkable rules.

    1. Prose fixes first: the multi-line commit message rule, the redirect reason, the "never remove a worktree by hand" line (it conflicts with an existing allow entry; item 3 of dotfiles #1556) and the "no gate.sh batch file" line (it conflicts with the allow entry that names batch).
    2. Set permissions.disableBypassPermissionsMode in the dotfiles settings source. No friction: bypass mode is never used.
    3. Foreground until and --watch waits: a plugin hook, not a dotfiles one, because a rule that changes what a stage permits belongs in a repository or plugin (AGENTS.md, "Team standards"). Strongest evidence: 741 and 217 hits in local transcripts (regex upper bounds).
    4. Deny rules in the dotfiles for the owner-specific ones: the dotfiles repository under the ghq root, and a plugin install with project or local scope.
    5. One Agent hook in the dotfiles that blocks a Haiku spawn (the routing policy is personal).

    Each prose line is removed once its check lands.

    Stay as prose: editing the chezmoi source instead of the rendered file, literal GitHub writes, and the shell shapes (VAR=, export, redirect): high friction, or already judged by the auto-mode classifier. On hold: no worktree or clone under temp, until the guardrails temp-repository exemption is reconciled.

    Basis:

    • The talk, slide 12, transcript 1:04:06 to 1:04:36, and slide 23, 1:10:19: every correction becomes a deterministic check.
    • Her correct skill: "If the rule was already there and nothing enforces it, that's a repeat, so fix it at the highest level in the same change" (pstack/skills/correct/SKILL.md:30).
    • The inventory was built by a read-only subagent; the absent bypass key and the existing git checkout -- and git reset --hard denies were confirmed by the main session.

    Open point for the build of item 3: whether a PreToolUse hook sees the Bash call's background flag in its input; read the hooks reference before building.

    Build: one plugin item here for the foreground-wait hook, filed when the map closes; the dotfiles changes are recorded on dotfiles #1556. Both feed the rule-to-enforcer inventory.

  6. kyle-sexton commented on Nov 13, 2026

    @kyle-sexton
    MemberAuthor

    Done (2026-11-13): Resolved; see the resolution comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.needs-owner-decisionAwaiting a human or maintainer judgment call.needs-triageNot yet classified. Floor until a type and one priority tier are set.wayfind: interviewWayfind decision item: contract/requirements call the user must make; human in the loop.

    Type

    Fields

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions