You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature Request: Full Code Base Audit vs Documentation #225
I would love to be able to do a full audit of the code base and compare it to the documentation of what should have been built, or what is yet to be built, to figure out the gaps that exist.
Not just for a specific feature, but for the entire project.
This is especially useful when I am starting a new session and I want to start spinning up 5 new workspaces in Conductor but I want to know what the current state of play is, so I can know where to start and what workspace should be working on what (so there isn't overlap).
Let me know if I am explaining it clearly.
P.S. I absolutely love this skill stack. It has been a legit gamechanger for me.
Addressed by /cso in #325 — run /cso for a full codebase security audit (OWASP Top 10, STRIDE threat model, attack surface mapping, data classification, dependency scanning). For documentation audits, use /document-release.
Activity
garrytan commentedon Mar 22, 2026
Addressed by /cso in #325 — run
/csofor a full codebase security audit (OWASP Top 10, STRIDE threat model, attack surface mapping, data classification, dependency scanning). For documentation audits, use/document-release.