fix: route users to /comply Autopilot, not the deprecated wrapper - #47
fix: route users to /comply Autopilot, not the deprecated wrapper#47aanishs wants to merge 1 commit into
Conversation
…o wrapper Post-#44 sweep per the comply-auto-deprecation-circular learning: gdpr/soc2/pci-dss recommendations and README flow diagram + skills table now point at /comply. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Greptile SummaryThis PR completes the post-#44 reference sweep, replacing the deprecated
Confidence Score: 4/5Safe to merge — all changes are documentation and templates with no runtime behavior affected. The sweep correctly removes the deprecated /comply-auto references across the six skill files. The only rough edge is in README.md: the notation /comply → Autopilot in both the skills table and the flow diagram implies a literal typed command, when the actual mechanism is a conversational prompt inside /comply. This won't break anything, but it will confuse new users trying to discover how to launch Autopilot mode. README.md — the skills table Command column entry and the flow diagram node both use a notation that reads as a literal command rather than a conversational mode selection. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["User types /comply"] --> B["comply/SKILL.md: persona detection + journey routing"]
B --> C{"Offer Autopilot?\n(Founder persona)"}
C -->|"Yes"| D["comply-auto/SKILL.md\n(Autopilot engine)"]
C -->|"No"| E["Manual commands\n/comply-scan, /comply-fix, /comply-assess"]
D --> F["Scan → Fix → Interview\none control at a time"]
F --> G["/comply-report → signed audit packet"]
style A fill:#2563eb,color:#fff
style D fill:#16a34a,color:#fff
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
A["User types /comply"] --> B["comply/SKILL.md: persona detection + journey routing"]
B --> C{"Offer Autopilot?\n(Founder persona)"}
C -->|"Yes"| D["comply-auto/SKILL.md\n(Autopilot engine)"]
C -->|"No"| E["Manual commands\n/comply-scan, /comply-fix, /comply-assess"]
D --> F["Scan → Fix → Interview\none control at a time"]
F --> G["/comply-report → signed audit packet"]
style A fill:#2563eb,color:#fff
style D fill:#16a34a,color:#fff
Reviews (1): Last reviewed commit: "fix: route users to /comply Autopilot, n..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| flowchart TD | ||
| A["You type /hipaa"] --> B["em-dash imports 59 HIPAA controls\nfrom the NIST 800-53 catalog"] | ||
| B --> C["You type /comply-auto"] | ||
| B --> C["You type /comply → Autopilot"] |
There was a problem hiding this comment.
"You type /comply → Autopilot" which reads as if the user enters that exact string. Since Autopilot is triggered conversationally after running /comply, the label is misleading.
| B --> C["You type /comply → Autopilot"] | |
| B --> C["You type /comply\n(choose Autopilot when prompted)"] |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
| |---------|-------------| | ||
| | `/comply` | Status dashboard — compliance score, next step recommendation | | ||
| | `/comply-auto` | **Autopilot.** Scans, fixes, interviews — one control at a time | | ||
| | `/comply` → Autopilot | **Autopilot.** Scans, fixes, interviews — one control at a time (`/comply-auto` is deprecated) | |
There was a problem hiding this comment.
/comply → Autopilot is not a typed command, so readers scanning the table for what to type will be confused — every other row in the column is a discrete slash command. In skills/comply/SKILL.md the actual mechanism is a conversational offer inside /comply ("Want me to handle everything?"), so the entry should reflect that this is a mode of /comply, not a separate invocation string.
| | `/comply` → Autopilot | **Autopilot.** Scans, fixes, interviews — one control at a time (`/comply-auto` is deprecated) | | |
| | `/comply` (Autopilot) | **Autopilot.** Scans, fixes, interviews — one control at a time. Type `/comply` and choose Autopilot when prompted (`/comply-auto` is deprecated) | |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
1 participant
Trust Sprint hygiene (T1). Post-#44 reference sweep: gdpr/soc2/pci-dss SKILL templates and the README (flow diagram + skills table) still steered users into the deprecated /comply-auto wrapper. All now route to /comply Autopilot mode. Regenerated SKILL.md files included; 190 tests green.
🤖 Generated with Claude Code