dev

Enforce fact-based, security-conscious coding rules across Codex CLI sessions.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/maosanhioro/dotfiles --skill dev-maosanhioro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev
Source: https://github.com/maosanhioro/dotfiles/tree/main/codex/skills/dev
Command: npx skills add https://github.com/maosanhioro/dotfiles --skill dev-maosanhioro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex sessions often lack consistent behavioral guidelines, leading to inconsistent answers, variable code quality, and security gaps. This Skill defines a personal development baseline that enforces fact-based responses, disciplined Git usage, coding quality standards, and security practices across all Codex workflows.

Core Features & Use Cases

  • Fact-based responses: require evidence and file reading before proposing edits.
  • Git and workflow discipline: promote reproducible changes and safer refactoring.
  • Coding quality & security: establish naming, error handling, testing, and secure coding rules across a project.
  • Use Case: in a code review, codify decisions with explicit references to project files and evidence.

Quick Start

Follow the Dev SKILL.md to activate these rules in every Codex session, ensuring consistent behavior by default.

Frequently Asked Questions about dev

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

FAQPage Schema
How do I enforce secure coding standards and fact-based responses in Codex sessions?

You can enforce secure coding standards in Codex by activating a rules-based Skill that requires file reading before edits, robust error handling, testing, and factual correctness across all CLI sessions and project workstreams.

What is the best way to ensure consistent code quality and security during Codex code reviews?

The best way to ensure consistent code quality during reviews is to codify decisions with explicit references to project files and evidence, applying a baseline that enforces clear naming, secure practices, and disciplined Git usage.

How do I stop Codex from making unverified code edits without reading the project files first?

To stop unverified edits, apply a behavioral guideline Skill that mandates fact-based responses and requires Codex to read files before proposing any refactoring, design proposals, or code modifications.

Can I apply a single set of coding guidelines across all Codex CLI workflows and refactoring tasks?

Yes, you can apply a single set of coding guidelines across all Codex CLI workflows by following the Dev SKILL.md to activate rules that ensure reproducible changes and safer refactoring by default.

Why does Codex provide inconsistent answers and variable code quality during project workstreams?

Codex provides inconsistent answers and variable code quality when sessions lack consistent behavioral guidelines, which you can resolve by defining a personal development baseline that enforces factual correctness and secure coding practices.

Are there limitations to using default Codex sessions for complex refactoring and secure coding?

Default Codex sessions lack enforced security practices and disciplined Git usage, limiting their ability to safely handle complex refactoring without a codified set of fact-based rules guiding the behavioral output.