one-way-door — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited one-way-door (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Some decisions are easy to reverse, you can change a UI component, rename a variable, or swap a utility function with no lasting consequences. These are two-way doors: walk through, and if it's wrong, walk back.
Other decisions create gravity. Once traffic, users, or other code depends on them, changing course gets expensive. A database schema migration after launch. An API contract that external consumers rely on. An auth boundary that shapes your entire permission model. These are one-way doors.
The most expensive mistakes in software aren't bugs. They're irreversible architectural decisions made too quickly.
Files matching: schema.prisma, schema.graphql, *.sql, migration*, models.py, models.ts, entities.py, entities.ts
Data models are the hardest decisions to reverse. Once your database has rows, every schema change requires a migration. Column renames break queries. Relationship changes cascade through your entire application.
Questions to ask:
Files matching: docker-compose*, Dockerfile, *.tf, terraform*, pulumi*, cdk*, cloudformation*, k8s*, kubernetes*, helm*
Infrastructure choices constrain everything built on top of them. Switching from ECS to Kubernetes, or from Lambda to containers, affects deployment pipelines, monitoring, scaling, and team knowledge.
Questions to ask:
Files matching: auth.{ts,js,py}, firestore.rules, storage.rules, *.rules, security.{ts,js,py,json,rules,yaml,yml}, rbac.{ts,js,py,json}, permissions.{ts,js,py,json}
These patterns are extension-qualified on purpose: an unrelated file that merely contains the word security or permissions (a note, a doc, a test) does not trip the check.
Auth boundaries are load-bearing walls. Session vs JWT, role-based vs attribute-based, single-tenant vs multi-tenant, each choice shapes your security model, user experience, and compliance posture.
Questions to ask:
Files matching: openapi*, swagger*, *.proto, *.graphql, api-schema*, routes.ts, routes.js, routes.py
Published APIs are promises to consumers. Breaking changes require versioning, deprecation periods, and migration guides. Internal APIs between services create coupling that's hard to unwind.
Questions to ask:
Files matching: events.ts, eventbus.ts, eventemitter.py, eventhandler.py, pubsub*, queue*, kafka*, rabbit*
Event schemas are contracts between producers and consumers. Once multiple services subscribe to an event, changing its shape requires coordinated deploys. Event ordering assumptions become architectural constraints.
Questions to ask:
Files in: .github/, .gitlab/, .circleci/, or matching Jenkinsfile, .travis.yml, cloudbuild*
CI/CD pipelines become the backbone of your release process. Teams build muscle memory around deploy workflows. Changing pipeline structure means retraining, and broken deploys during the transition can block your entire team.
Questions to ask:
Files matching: package.json, Cargo.toml, go.mod, requirements.txt, pyproject.toml, Gemfile
Framework and dependency choices ripple through your entire codebase. Switching from React to Vue, or from Express to Fastify, means rewriting large portions of your application.
Questions to ask:
Files matching: firebase.json, .firebaserc, firestore.indexes*
Cloud service configs lock you into specific providers and architectures. Firestore indexes determine query performance. Firebase rules define your security boundary.
Questions to ask:
These file types are safe to decide quickly and change later:
.env, feature flags, app configThe optional Claude Code hook has an early-exit safelist before any pattern check. Tests, fixtures, mocks, Markdown, and documentation or plan text files pass even when a filename contains a word such as auth or security.
The shared skill does not depend on this hook. Apply the same safelist when you review a proposed file manually.
Add this rule to the project's canonical instruction file. Use AGENTS.md for Codex or CLAUDE.md for Claude Code. If one imports the other, edit the canonical file.
### One-way door check
Before creating a file that represents an architectural decision, ask which
parts would be difficult to reverse. One-way doors include data models, service
communication patterns, authentication boundaries, tenancy models, and
infrastructure configuration. If a decision is a one-way door, ask the user and
wait for an explicit answer. Use the client's structured question tool when it
has one. Explain the trade-offs and at least two alternatives before asking
whether to proceed. Two-way doors, such as UI components, utilities, and
styling, can be changed quickly.This manual workflow is the portable behavior. It works without automatic hooks:
question tool when it has one.
Claude Code users may install the repository's one-way-door-check hook for automatic pre-write blocking. The hook and its approval promoter are optional Claude Code enforcement, not shared Agent Skills behavior. The adapter keeps a session-scoped pending and approved ledger so an approved file can be retried without a loop.
PowerShell ports, one-way-door-check.ps1 and one-way-door-approve.ps1, are included in this skill directory. The hook documentation contains the POSIX implementation, the ledger rules, and the Claude Code wiring. Clients without this adapter must use the manual workflow above. Do not treat the absence of automatic enforcement as approval.
Before committing to any one-way door, ask:
If you can't answer these questions clearly, you're not ready to walk through the door.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.