developer

Codify development best practices for GitHub Agentic Workflows modules.

4.9k|489|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/github/gh-aw --skill developer-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer
Source: https://github.com/github/gh-aw/tree/main/skills/developer
Command: npx skills add https://github.com/github/gh-aw --skill developer-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The developer Instructions for GitHub Agentic Workflows (gh-aw) consolidate technical specifications and development guidelines to enable consistent code organization, validation architecture, security practices, and implementation patterns across the project.

Core Features & Use Cases

  • Governance of code organization: guidance on structuring files, packages, and modules.
  • Validation and security: central validation architecture, strict mode, and safety best practices to ensure secure, reliable workflows.
  • Lifecycle and release: guidance on release management, testing, and documentation to support maintainable improvements and governance.

Quick Start

Use the developer skill as a template to structure a new gh-aw module following the documented organization, validation, and security patterns.

Frequently Asked Questions about developer

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

FAQPage Schema
What are development guidelines for GitHub Agentic Workflows?

Development guidelines for GitHub Agentic Workflows codify code organization, validation architecture, and security practices to ensure consistent, secure, and maintainable module implementation across the project.

How do I structure a new gh-aw module?

To structure a new gh-aw module, use the developer skill as a template to organize files and packages, applying the documented validation architecture and strict mode security patterns for reliable workflows.

How does validation architecture work in agentic workflow code?

Validation architecture in agentic workflow code uses frontmatter with required name and description fields, plus optional scripts and references, to enable automated validation and self-contained guidance.

Can I use these development patterns for release management?

Yes, these development patterns include lifecycle and release guidance covering release management, testing, and documentation to support maintainable improvements and governance across all modules.

Do I need safe-output patterns for secure workflow development?

Yes, safe-output patterns are required for secure workflow development, forming part of the central validation architecture and safety best practices to ensure reliable and secure code execution.

What's the best way to govern code organization across modules?

The best way to govern code organization across modules is to apply structured guidance on file, package, and module structuring, ensuring consistency and maintainable improvements throughout the project.