Skip to content

Review Config Hardening #55

Open
Open

Description

@flyingrobots

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/PROCESS_review-config-hardening.md
Original lane: cool-ideas
Original legend: PROCESS

Original backlog card

Harden repo review configuration so automated review tools understand
METHOD's actual structure: process docs, design docs, retros, witness
artifacts, backlog lanes, and command/code boundaries. The aim is less
noise, better path-specific guidance, and fewer false "missing
contract" reviews.

Session context:

  • PR review of method drift surfaced several configuration-level
    recommendations: fix dead guideline paths, add path instructions,
    define custom checks for cycle closeout, and filter evidence-heavy
    witness files from noisy line comments.
  • Those recommendations are not all equally urgent, but together they
    point at a real gap between METHOD's repo shape and what review bots
    are being told to expect.

What this surfaced:

  • Repo structure should be teachable to review tooling, not just to
    humans.
  • Path-aware guidance and custom checks could make automated review much
    more aligned with METHOD's doctrine.
  • This is review-surface hardening, not product behavior, so it should
    stay behind more urgent repo-health work like CI and code structure.

Activity

  1. coderabbitai commented on Jun 1, 2026

    @coderabbitai
    🔗 Related PRs

    #5 - Shape release workflow and user migration docs [merged]
    #6 - Automated Witness Capture (Cycle 0020) [merged]
    #18 - Land 0030-0033 repo-truth and MCP debt fixes [merged]
    #20 - Add backlog notes for agent-first planning and review workflow [merged]
    #21 - Align test taxonomy fixtures with live legends [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!

  2. added
    needs-designNeeds or is missing a Method design artifact.
    type:maintenanceMaintenance, cleanup, or operational workflow work.
    on Jun 1, 2026
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.legend:processMethod process, workflow, adapters, and CLI work.needs-designNeeds or is missing a Method design artifact.type:maintenanceMaintenance, cleanup, or operational workflow work.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions