Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By carainc
Guides developers through a structured, compliant feature workflow (Research, Propose, Plan, Implement, Test, Secure) for healthcare software, with automated security compliance gates (HIPAA, SOC2, HITRUST) against uncommitted changes and optional Linear issue integration.
npx claudepluginhub carainc/reppit-health --plugin reppit-healthImplement the work described in an issue or task.
Break the chosen proposal into a concrete implementation plan.
Generate two solution proposals grounded in existing research and a feature or project request.
Run the full RePPITS workflow: Research → Propose → Plan → Implement → Test → Secure.
Research and document the existing codebase exactly as it is today; no suggestions or evaluations.
A Claude Code plugin that runs a secure development workflow for healthcare software.
RePPIT Health implements the RePPITS methodology, Research, Propose, Plan, Implement, Test, Secure, extending the RePPIT framework by Mihail Eric (Head of AI, creator of Stanford's first AI software engineering course) with HIPAA, SOC2, and HITRUST compliance gates for healthcare and healthtech teams.
Seven slash commands, available in Claude Code, Cursor, and any client that supports the Claude Code plugin spec:
| Command | What it does |
|---|---|
/reppit <topic-or-issue> | Run the full Research → Propose → Plan → Implement → Test → Secure workflow, with explicit approval gates between phases |
/research-codebase | Document the existing codebase exactly as it is today (no suggestions, no RCA) |
/make-proposals | Generate up to two solution proposals grounded in research |
/make-plan | Break the chosen proposal into ordered Linear issues (or local plans/*.md if Linear MCP is not configured) |
/implement <issue> | Implement a single Linear issue, with optional Ralph Loop mode |
/review-code | Review all uncommitted changes, post findings to Linear |
/secure | Run HIPAA, SOC2, and HITRUST checklists against your diff, separating code-verifiable findings from organizational controls |
Research --> Propose --> Plan --> Implement --> Test --> Secure --> Done
^ ^ ^ ^ ^ |
| refine | refine | refine | fix loop | fix |
└────┘ └────┘ └────┘ └────┘ └──┘ |
^ |
└── fix & test ───┘
In Claude Code (≥ 1.0.33):
/plugin marketplace add carainc/reppit-health
/plugin install reppit-health@carainc-reppit-health
That's it. The slash commands are immediately available.
git clone https://github.com/carainc/reppit-health.git
Then in Claude Code:
/plugin marketplace add ./reppit-health
/plugin install reppit-health@carainc-reppit-health
Useful for trying changes before pushing.
In any project directory:
/reppit Add a patient intake form
or with a Linear issue:
/reppit CAR-123
The plugin walks Research → Propose → Plan → Implement → Test → Secure and pauses at each gate for your approval. You can also invoke any phase directly, e.g. /secure to audit current uncommitted changes without running the full flow.
Checklists live in compliance/ inside the installed plugin:
hipaa-checklist.md — Administrative, physical, and technical safeguards (§164.308-312), PHI detection, minimum necessary, BAA verification, breach notification, telehealth compliancesoc2-checklist.md — All Trust Service Criteria (CC1-CC9), Availability (A1), Confidentiality (C1), Processing Integrity (PI1), Privacy (P1), plus injection prevention and secrets managementhitrust-checklist.md — All 14 CSF v11 control categories (00-13): access control, risk management, encryption, operations, incident management, business continuity, privacy practices, cross-tenant isolationorg-controls-audit.md — Schedule and tracking for organizational controls that can't be verified from code aloneEach item gets a PASS / WARN / FAIL / SKIPPED status. Items marked [org] (physical safeguards, board oversight, BAAs with subprocessors) are surfaced separately so they don't get auto-passed by a green diff.
If you want to customize a checklist for a specific repo, drop a file at .claude/compliance/<framework>-checklist.md in that workspace. /secure reads workspace overrides first, then falls back to the plugin's defaults.
If the Linear MCP is configured in Claude Code, the plugin will:
/implement <issue-id>/make-planIf Linear is not configured, the plugin falls back to local .md files in research/, plans/, and the conversation transcript. Both modes work end-to-end.
Apache 2.0, see LICENSE.
Share bugs, ideas, or general feedback.
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Security agents — security, compliance, privacy specialists
Check HIPAA compliance
Regulatory compliance verification for GDPR, SOC2, and HIPAA
Engineering process for solo founders and teams up to 50 engineers. Agents do architecture, code review, QA, and security. You make two decisions per feature.
AI-powered development workflow automation - Phase-based planning, implementation orchestration, preflight code quality checks with security scanning, ship-it workflow, and development principles generator for CLAUDE.md
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claim