Skip to content

Method drift check as pre-push hook #80

Open
Open
Method drift check as pre-push hook#80
Labels
lane:cool-ideasInteresting but not committed work.

Description

@flyingrobots
flyingrobots
opened on Jun 1, 2026

Migrated from Method backlog

This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.

Source backlog: docs/method/backlog/cool-ideas/PLATFORM_method-drift-as-pre-push-hook.md
Original lane: cool-ideas
Original legend: PLATFORM

Original backlog card

Method drift check as pre-push hook

Status: active cool idea. Echo documents cargo xtask method drift [cycle] as
planned, but cargo xtask method --help exposes only status today. The
canonical pre-push hook delegates through scripts/hooks/pre-push to
.githooks/pre-push; no Method drift gate is wired there yet. The external
/Users/james/git/method repo already has drift detection, so the remaining
work is choosing whether Echo calls the external Method CLI or implements the
Rust xtask command first.

Once cargo xtask method drift exists, wire it into
scripts/hooks/pre-push so playback questions are checked against
test descriptions before code leaves the machine.

Activity

  1. flyingrobots
    added
    lane:cool-ideasInteresting but not committed work.
    on Jun 1, 2026

  2. coderabbitai commented on Jun 1, 2026

    @coderabbitai
    coderabbitaibot
    on Jun 1, 2026 – with coderabbitai
    🔗 Related PRs

    flyingrobots/echo#15 - devcontainer: VS Code container with Rust stable+MSRV, Node 20, gh CLI [merged]
    flyingrobots/echo#308 - feat: begin PR workflow hardening [merged]
    flyingrobots/echo#309 - feat: add Doghouse PR flight recorder [merged]
    flyingrobots/echo#385 - docs(backlog): two follow-ups from the 2026-05-30 merge session [merged]
    flyingrobots/echo#388 - docs(method): add backlog cards and hook failure note [merged]

    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan
    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
  auto_enrich:
    enabled: false

    💬 Have feedback or questions? Drop into our discord!

  3. flyingrobots
    transferred this issue fromflyingrobots/echoon Jul 3, 2026

  4. coderabbitai commented on Jul 3, 2026

    @coderabbitai
    coderabbitaibot
    on Jul 3, 2026 – with coderabbitai
    🔗 Related PRs

    #2 - Add drift detector command and close out cycle 0005 [merged]
    #6 - Automated Witness Capture (Cycle 0020) [merged]

    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan
    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
  auto_enrich:
    enabled: false

    💬 Have feedback or questions? Drop into our discord!

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

    lane:cool-ideasInteresting but not committed work.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions