Four engineering skills, one plugin.
ttt-workflows bundles pr-review, sec-audit, trp, and copy-audit: four self-contained skills that review a pull request, run a security audit, deliver a ticket, or audit the copy end to end, from inside Claude Code. Read-only by default; anything that writes waits for your approval.
/plugin marketplace add kaelys-js/ttt-workflows/plugin install ttt-workflows- issue — PATCH /users/:id has no object-level authzusers.controller.ts:88
- suggestion — Empty string slips past the filter, widening the queryrepo.ts:41
- nitpick — Comment restates the code instead of the whytoken.ts:12
Four skills
Each is self-contained and portable across any repo and any tenant, with no client data baked in.
/pr-review/sec-audit/trp/copy-auditInstall once
Two commands in Claude Code, then invoke a skill whenever you need it.
Add the marketplace
Point Claude Code at the git-backed marketplace once. It stays available for every project.
/plugin marketplace add kaelys-js/ttt-workflowsInstall the plugin
Install ttt-workflows and all four skills register at once. Nothing else to set up.
/plugin install ttt-workflows/pr-reviewPaste a pull-request URL and ask for a review./sec-auditPoint it at a repo, a PR, a path, or a live tenant, and name a mode: sweep, review, poc, or remediate./trpHand it a ticket URL; it grounds the work, presents a plan, and stops for approval./copy-auditPoint it at a repo or a diff for a copy and microcopy pass; add--mode=commentsto sweep code comments and test names.
Watch each skill run
A short, synthetic run of each skill, played inside a Claude Code session — the same transcript, with motion off.
- Reading the diff — 6 files, +214 −38 …
- Checking each finding against the code …
- Request changes· 1 blocking, 2 non-blocking
- issue — PATCH /users/:id has no object-level authzusers.controller.ts:88
- suggestion — Empty string slips past the filter, widening the queryrepo.ts:41
- nitpick — Comment restates the code instead of the whytoken.ts:12
- Nothing posted — the review is handed back for you to paste.
- Sweeping source & IaC, live Azure, identity & CI …
- Three layers swept
- Source / IaC — semgrep · gitleaks · osv · checkov
- Live Azure — firewall · TLS floor · Key Vault
- Entra / ADO — app-regs · pipeline secrets
- High· SEC-07 · CVSS 8.2
- Postgres reachable from 0.0.0.0 — public network access enabled.
- Private advisory drafted. Read-only until you approve disclosure.
- Grounding the ticket in the repo …
- Plan · phases 0–5
- Found in the repo — auth.middleware.ts:44, no rate limiter mounted
- Change: mount the limiter, add a regression test
- Verify: format · lint · affected tests · build — all green
- PR opened on GitHub; ticket updated in both layers
- Waiting for your approval before anything runs.
- Extracting strings, judging each in full-file context …
- 142 strings reviewed · four content pillars
- 128 keep · 9 rewrite · 5 flag
- rewrite · microcopy — "Click here to get started" → "Get started"hero.astro:12
- flag · inclusive — "sanity check" needs a house-style calldocs/setup.md:38
- Rewrites proposed — nothing is written until you approve.
Operator's playbooks
Each skill ships a companion PDF: the what, how, and why of doing that work by hand.
Questions
What is ttt-workflows?
Do I have to trust it with my repo?
Is it really read-only?
Does it work on GitHub and Azure DevOps?
How do updates work through the marketplace?
What does copy-audit review, and how does it avoid breaking code?
Is my data sent anywhere?
/plugin marketplace add kaelys-js/ttt-workflows/plugin install ttt-workflows