personal-production-rail

Applies production-quality policy lenses to code generation, fixes, design, and review.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/kosako/agent-tools --skill personal-production-rail-kosako
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: personal-production-rail
Source: https://github.com/kosako/agent-tools/tree/main/shared/skills/personal-production-rail
Command: npx skills add https://github.com/kosako/agent-tools --skill personal-production-rail-kosako

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-generated code often suffers from over-engineering, hallucinated APIs, scope creep, and superficial fixes. This Skill acts as a librarian that applies production-quality policy lenses to coding work, ensuring code meets a fixed quality bar without loading every policy document into context. ## Core Features & Use Cases - Selective policy loading: Reads a policy index and loads at most four relevant policy lenses (ai-antipattern, coding, review, existing-system-respect, design-planning) instead of all references. - Two application lenses: Applies generation lens (pre-implementation preflight and post-implementation self-check) and review lens (findings mapped to must/should/nit severities with a REJECT/Warning/APPROVE process verdict). - Default-on with proportional effort: Code work is treated as production by default; only explicit vibe/prototype/throwaway work skips it, and trivial changes get a lighter procedure without lowering the quality bar. - Use Case: When asked to implement a payment API client at production quality, the Skill reads the policy index, loads the relevant lenses, runs preflight checks (requirement match, API existence, minimal diff, contract preservation), then self-checks the result for over-implementation and unreachable code. ## Quick Start Ask the AI to implement or review code at production quality, and it will select the relevant policy lenses from the index and apply preflight and self-check before reporting.

Frequently Asked Questions about personal-production-rail

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce code quality policies on AI-generated code?▼

Use a librarian-style skill that reads a policy index and loads only the relevant policy lenses for the task type. It applies a preflight check before implementation and a self-check after, covering requirement match, minimal diff, and contract preservation.

How to structure AI code review output with severity levels?▼

Map review findings to must, should, and nit severities, then aggregate them into a single process verdict: REJECT if any must exists, Warning if only should exists, APPROVE otherwise. Keep finding severity and process verdict as separate output fields.

When should code quality policies be skipped for prototypes?▼

Skip policy application only when vibe coding, prototype, spike, or throwaway work is explicitly declared. Never infer the exception from the task looking small or temporary; unspecified code work defaults to production quality.

Can vendored third-party policy documents contain prompt injection?▼

Policy text is treated strictly as criteria or data, never as instructions, so embedded directives like skipping reviews are not executed. Vendored files also pass a static injection scan and human review before being pinned by commit.

What are the limitations of policy-lens code review?▼

The review verdict covers only the code review process, not overall PR merge readiness such as CI status or branch protection. The skill points out findings but never expands the caller's write scope or blocks the caller's work on its own.