Run any Skill in Manus with one click

orbitant-12-factor

Stars5

Forks0

UpdatedApril 28, 2026 at 07:11

Use when checking if a repo follows 12-factor app principles — config stored in env vars (not hardcoded), dependency lockfiles present, CI pipeline separation, structured logging to stdout, or dev/prod environment parity. Activates when someone asks about 12-factor compliance, deployment readiness, or config management practices in a Node.js or Python project. Also trigger when someone notices hardcoded localhost URLs, missing .env.example, or asks "is this deploy-ready?" — even without mentioning 12-factor explicitly.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

weorbitant

weorbitant/orbitant-os

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	orbitant-12-factor
description	Use when checking if a repo follows 12-factor app principles — config stored in env vars (not hardcoded), dependency lockfiles present, CI pipeline separation, structured logging to stdout, or dev/prod environment parity. Activates when someone asks about 12-factor compliance, deployment readiness, or config management practices in a Node.js or Python project. Also trigger when someone notices hardcoded localhost URLs, missing .env.example, or asks "is this deploy-ready?" — even without mentioning 12-factor explicitly.
version	0.1.0
license	MIT
metadata	{"author":"orbitant","tags":"engineering, audit, 12-factor, config, deployment, ci, logging"}

Overview

Audits the statically-verifiable subset of 12-factor app compliance. Only factors observable from the repo are scored — runtime factors are listed as "not checked" with an explanation.

When to Use

Assessing deployment readiness of a new project
Checking config management practices (hardcoded URLs, missing .env.example)
Reviewing CI pipeline separation
Running a section audit after /orbitant-engineering:ground-control flagged 12-factor issues

How to Run

Load the reference standards:

@plugins/orbitant-engineering/skills/12-factor/references/12-factor.md

Detect the stack first:

ls package.json requirements.txt pyproject.toml 2>/dev/null

Then run checks for all statically-verifiable factors. Note which factors were skipped and why.

Output Format

## 12-Factor Compliance   {rating}

### Passing
- II. Dependencies: lockfile present (package-lock.json), versions pinned
- V. Build/release/run: CI pipeline defined (.github/workflows/)

### Failing
- III. Config: hardcoded URLs found in source
  Finding: "http://localhost:3000" in src/api/client.js:8
  Recommendation: move to process.env.API_URL, add to .env.example

### Not checked (requires runtime)
- Factors I, IV, VI, VII, VIII, IX, XII
  Reason: not observable from static repo analysis

Rating: ⚠️ Partial

Ratings: ❌ Not compliant / ⚠️ Partial / ✅ Good / 🚀 Fully observable compliance

See references/12-factor.md for full criteria and excluded factors explanation.

More from this repository

same repository

orbitant-end-learn

weorbitant/orbitant-os

Use when the user is done learning for the day, wants to save progress, or wants to wrap up a lesson. Also triggered by /learn when postponing or abandoning. Updates the learning intelligence layer (insights.md) after each session. Triggers on: "end session", "done learning", "save progress", "wrap up", "end-learn", "I'm done for today".

2026-06-055

orbitant-init-learning

weorbitant/orbitant-os

Use when the user wants to set up or update their learning profile, configure learning preferences, update their role or gaps, add feedback from reviews or 1:1s, or when any other learning skill detects no profile exists. Triggers on: "set up learning", "update my learning profile", "init learning", or pasting performance feedback.

2026-06-055

orbitant-learn

weorbitant/orbitant-os

Use when the user wants to sit down and learn, continue a lesson, practice a skill, or work through a learning project. Triggers on: "let's learn", "continue my lesson", "start learning", "practice", "I have time to learn", or "pick up where I left off".

2026-06-055

orbitant-learning-insights

weorbitant/orbitant-os

Internal-only skill — never called directly by users. Provides the Learning Intelligence Layer. Two modes: "build context" (called by /learn at session start) reads learning history and produces a learner context; "update insights" (called by /end-learn after session close) updates the persistent insights.md summary.

2026-06-055

orbitant-learning-report

weorbitant/orbitant-os

Use when the user wants to review what they've learned, see progress on their gaps, get a summary of recent learning sessions, or wants article ideas based on learnings. Triggers on: "learning report", "what have I learned", "progress report", "summarize my learning", or "learning summary for the last month".

2026-06-055

orbitant-learning-status

weorbitant/orbitant-os

Use when the user wants a fast status check on their learning without a full report. Triggers on: "learning status", "where am I", "what's my learning state", "how's my learning going", or "check my progress".

2026-06-055

name	orbitant-12-factor
description	Use when checking if a repo follows 12-factor app principles — config stored in env vars (not hardcoded), dependency lockfiles present, CI pipeline separation, structured logging to stdout, or dev/prod environment parity. Activates when someone asks about 12-factor compliance, deployment readiness, or config management practices in a Node.js or Python project. Also trigger when someone notices hardcoded localhost URLs, missing .env.example, or asks "is this deploy-ready?" — even without mentioning 12-factor explicitly.
version	0.1.0
license	MIT
metadata	{"author":"orbitant","tags":"engineering, audit, 12-factor, config, deployment, ci, logging"}

Overview

Audits the statically-verifiable subset of 12-factor app compliance. Only factors observable from the repo are scored — runtime factors are listed as "not checked" with an explanation.

When to Use

Assessing deployment readiness of a new project
Checking config management practices (hardcoded URLs, missing .env.example)
Reviewing CI pipeline separation
Running a section audit after /orbitant-engineering:ground-control flagged 12-factor issues

How to Run

Load the reference standards:

@plugins/orbitant-engineering/skills/12-factor/references/12-factor.md

Detect the stack first:

ls package.json requirements.txt pyproject.toml 2>/dev/null

Then run checks for all statically-verifiable factors. Note which factors were skipped and why.

Output Format

## 12-Factor Compliance   {rating}

### Passing
- II. Dependencies: lockfile present (package-lock.json), versions pinned
- V. Build/release/run: CI pipeline defined (.github/workflows/)

### Failing
- III. Config: hardcoded URLs found in source
  Finding: "http://localhost:3000" in src/api/client.js:8
  Recommendation: move to process.env.API_URL, add to .env.example

### Not checked (requires runtime)
- Factors I, IV, VI, VII, VIII, IX, XII
  Reason: not observable from static repo analysis

Rating: ⚠️ Partial

Ratings: ❌ Not compliant / ⚠️ Partial / ✅ Good / 🚀 Fully observable compliance

See references/12-factor.md for full criteria and excluded factors explanation.