What problem does it solve? Teams lose the reasoning behind coding conventions and invariants because the 'why' lives only in PR discussions and commit messages. This Skill automates the drafting of rules-with-why so knowledge is captured as drafts while humans keep final ratification control. ## Core Features & Use Cases - Forward capture: After a meaningful change or PR, the agent reads the diff, commit message, and session context to draft rules with their rationale into .fux/CANDIDATES.md. - Retroactive mining: Run $FUX propose-rules --retro to surface latent invariants from the AST and recover the why from git commit subjects, with no LLM cost. - Human-gated triage: Review drafts with fux candidates --pending, then accept or reject each one; constitutional rules are never auto-accepted and route through fux ratify. - Use Case: After merging a PR that switches lot accounting to average-cost, the agent drafts a convention rule citing PR #41 as the why, which a maintainer later ratifies. ## Quick Start Ask the agent to propose rules from the changes in your latest pull request and file them as drafts for review.
