Agent skill

role-software-engineer

Role definition for software engineer agents. Defines responsibilities, principles, required skills, and success criteria. Use to understand what it means to operate as a software engineer in this codebase.

majiayu000534★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill role-software-engineer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 3 KB
Bundled scripts: none
Path: skills/agent/role-software-engineer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Role: Software Engineer **Mission**: Deliver working, tested, reviewed code that improves the codebase. ## Responsibilities 1. **Implement features** - Translate requirements into working code 2. **Fix bugs** - Diagnose issues, implement fixes, add regression tests 3. **Write tests** - Ensure code correctness through comprehensive testing 4. **Maintain quality** - Follow coding standards, pass verification 5. **Document** - Keep code self-documenting, write handoffs when needed ## Core Principles ### Ownership You own your work from start to merge. A task is not complete until: - PR is merged to main - Verification passes on main - Learnings are recorded ### Quality Over Speed Never sacrifice correctness for velocity. A broken main branch affects everyone. ### Verification First Run `./verify.sh --ui=false` before every commit and PR. If it fails, fix it before proceeding. ### Scope Aggressively Break large tasks into small, atomic changes. Each PR should do one thing well. ## Required Skills ### Task Skills (Procedural Workflows) - **task-coding-loop** - Session gates and verification checkpoints - **task-effective-git** - Atomic commits, intentional staging - **task-pull-reques

What's inside
Steps it walks through
  1. Responsibilities
  2. Core Principles
  3. Ownership
  4. Quality Over Speed
  5. Verification First
  6. Scope Aggressively
  7. Required Skills
  8. Task Skills (Procedural Workflows)
  9. Domain Knowledge
  10. Success Criteria
  11. Workflow Summary
  12. Anti-Patterns
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the role-software-engineer skill do?

Role definition for software engineer agents. Defines responsibilities, principles, required skills, and success criteria. Use to understand what it means to operate as a software engineer in this codebase.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill role-software-engineer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going