senior-engineer

Enforce rigorous engineering practices across code, infrastructure, and documentation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/leonardofhy/openclaw-workspace --skill senior-engineer-leonardofhy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-engineer
Source: https://github.com/leonardofhy/openclaw-workspace/tree/main/exports/starter-kit/skills/senior-engineer
Command: npx skills add https://github.com/leonardofhy/openclaw-workspace --skill senior-engineer-leonardofhy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Senior Engineer Mode — enforce rigorous engineering practices for ALL work: code, infrastructure, protocols, and documentation. Use when (1) building new features or scripts, (2) fixing bugs with proper root cause analysis, (3) refactoring for maintainability, (4) making architecture decisions, (5) designing protocols or system changes, (6) modifying shared infrastructure, (7) spawning coding agents that need higher quality output. NOT for quick one-liner fixes, reading/exploring code, or non-coding tasks.

Core Features & Use Cases

  • Ship changes that are verified, safe, and synced.
  • Classify work before writing: New code, Modify existing system, Infra / automation / shared state.
  • Enforce evidence-driven verification, Git hygiene, and safety rails across projects.

Quick Start

Choose a classification (A, B, or C) for your change, run verification commands, and commit with a traceable branch.

Frequently Asked Questions about senior-engineer

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

FAQPage Schema
How do I enforce root cause analysis for bug fixes in my codebase?

To enforce root cause analysis for bug fixes, this Skill requires classifying modifications and applying evidence-driven verification before committing. It mandates rigorous engineering practices to ensure changes are verified, safe, and synced across the project.

What is the best way to maintain git hygiene during infrastructure changes?

Maintaining git hygiene during infrastructure changes requires enforcing traceable branches and safety rails. This Skill classifies shared state modifications and mandates strict git workflow synchronization to ship verified infrastructure automation safely.

How do I set up safety rails for spawning coding agents?

Setting up safety rails for coding agents requires enforcing rigorous engineering practices across all generated outputs. This Skill mandates evidence-driven verification and strict git hygiene to ensure agent-produced code meets senior-engineer quality standards.

When should I not use rigorous engineering practices for code modifications?

You should not use rigorous engineering practices for quick one-liner fixes, reading or exploring code, or non-coding tasks. This Skill is explicitly built for feature development, refactoring, and infrastructure changes requiring root cause analysis.

Does this engineering workflow require a specific SKILL.md format?

Yes, this engineering workflow requires a mandatory frontmatter with name and description in SKILL.md. It supports optional scripts, references, and assets to define verification, git hygiene, and safety rails for your project.