role-software-engineer

Apply software engineer principles and success criteria to development workflows.

1|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/Anveio/conveaux --skill role-software-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-software-engineer
Source: https://github.com/Anveio/conveaux/tree/main/.claude/skills/role-software-engineer
Command: npx skills add https://github.com/Anveio/conveaux --skill role-software-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines the role, responsibilities, principles, and success criteria for software engineer agents.

Core Features & Use Cases

  • Role Definition: Automatically apply software engineer principles and responsibilities.

Core Features & Use Cases

  • Success Metrics: Automatically track PR throughput, verification pass rates, and main branch health automatically.

Quick Start

Use this Skill to understand what it means to operate as a software engineer in this codebase.

Quick Start

Invoke this Skill to understand software engineer responsibilities, required skills, and success criteria automatically.

Quick Start

Use this Skill when you need to understand the role and responsibilities of a software engineer agent.

Quick Start

Use this Skill to automatically apply software engineer principles and success criteria to your work.

Frequently Asked Questions about role-software-engineer

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

FAQPage Schema
What are the core responsibilities of a software engineer in a collaborative workflow?

Software engineer responsibilities center on delivering working, tested, reviewed code that improves the codebase. This includes feature implementation, bug fixing, testing, documentation, atomic commits, disciplined PR workflows, and verification-first development to maintain main branch health.

How do I apply software engineer success criteria to my development work?

Apply success criteria by following verification-first development: write tests before or alongside code, ensure all PRs pass review, make atomic commits with clear intent, and maintain comprehensive documentation. Track PR throughput, verification pass rates, and main branch health as metrics.

What defines role clarity for software engineers on a team?

Role clarity eliminates ambiguity by defining specific responsibilities: deliver tested, reviewed code; participate in atomic commit discipline; follow PR workflows; and maintain testing and documentation standards. This Skill automatically applies these principles to establish consistent expectations.

Can I use verification-first development across different types of code changes?

Yes. Verification-first development applies to feature implementation, bug fixes, testing, and documentation across software projects. The approach scales from small hotfixes to large features while maintaining consistent quality and traceability through atomic commits and PR reviews.

Why does disciplined PR workflow matter for codebase health?

Disciplined PR workflows protect main branch health by enforcing code review, testing verification, and atomic commit practices before merging. This prevents untested or undocumented changes from degrading the codebase and creates clear accountability and traceability for all changes.