Codex

contribute-start

Initialize an AIWG contribution workflow by creating a feature branch, configuring DCO, and linking a tracking issue

104 stars

Best use case

contribute-start is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

It is a strong fit for teams already working in Codex.

Initialize an AIWG contribution workflow by creating a feature branch, configuring DCO, and linking a tracking issue

Teams using contribute-start should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/contribute-start/SKILL.md --create-dirs "https://raw.githubusercontent.com/jmagly/aiwg/main/.agents/skills/contribute-start/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/contribute-start/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How contribute-start Compares

Feature / Agentcontribute-startStandard Approach
Platform SupportCodexLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Initialize an AIWG contribution workflow by creating a feature branch, configuring DCO, and linking a tracking issue

Which AI agents support this skill?

This skill is designed for Codex.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Contribute Start

You initialize a contribution workflow for AIWG itself: create a feature branch, configure DCO (Developer Certificate of Origin), link to a tracking issue, and set up a working directory for the contribution.

## Triggers

Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):

- "I want to add a feature to AIWG" → init contribution for new feature
- "set up my branch for this fix" → init contribution for bug fix
- "how do I contribute?" → explain contribution flow and offer to initialize
- "start a PR" → initialize contribution and set up branch

## Trigger Patterns Reference

| Pattern | Example | Action |
|---------|---------|--------|
| Contribute start | "contribute start" | Run `aiwg contribute-start` |
| New contribution | "new contribution" | Run `aiwg contribute-start` |
| Init contribution | "init contribution" | Run `aiwg contribute-start` |
| Start contributing | "start contributing to aiwg" | Run `aiwg contribute-start` |
| With issue | "start contribution for issue #42" | Run `aiwg contribute-start --issue 42` |
| With description | "start a contribution for adding voice support" | Run `aiwg contribute-start --description "adding voice support"` |

## Behavior

When triggered:

1. **Extract intent**:
   - Is there an issue number to link? (e.g., "for issue #42")
   - Is there a description to use for the branch name?
   - What type of contribution: feature, fix, docs, refactor?

2. **Run the appropriate command**:

   ```bash
   # Default: interactive contribution initialization
   aiwg contribute-start

   # Link to a specific tracking issue
   aiwg contribute-start --issue 42

   # With branch description (slugified automatically)
   aiwg contribute-start --description "add voice support to deploy command"

   # Specify contribution type
   aiwg contribute-start --type feat
   aiwg contribute-start --type fix
   aiwg contribute-start --type docs
   ```

3. **Report the result** — confirm the branch name, DCO status, and working directory path.

## What Gets Set Up

| Step | What Happens |
|------|-------------|
| Branch creation | `feat/<slug>` or `fix/<slug>` branch created from latest `main` |
| DCO config | `.git/hooks/commit-msg` DCO hook installed if not present |
| Working directory | `.aiwg/working/contributions/<branch-name>/` created for drafts |
| Issue link | Branch description references issue number if provided |
| Contribution notes | `CONTRIBUTING.md` read and summarized for context |

## DCO Note

AIWG contributions require a Developer Certificate of Origin sign-off on each commit:

```
Signed-off-by: Your Name <your@email.com>
```

The `contribute-start` command installs a commit-msg hook that reminds you to include this. Pass `-s` to `git commit` to sign off automatically.

## Examples

### Example 1: Starting a feature contribution

**User**: "Start a contribution — I want to add cost tracking to the ralph command"

**Extraction**: Feature contribution, description provided

**Action**:
```bash
aiwg contribute-start --type feat --description "add cost tracking to ralph command"
```

**Response**: "Contribution initialized. Branch: `feat/add-cost-tracking-to-ralph-command`. DCO hook installed. Working directory: `.aiwg/working/contributions/feat-add-cost-tracking-to-ralph-command/`. Sign your commits with `git commit -s`."

### Example 2: Contribution linked to an issue

**User**: "Start contribution for issue #312"

**Extraction**: Linked to issue 312

**Action**:
```bash
aiwg contribute-start --issue 312
```

**Response**: "Contribution initialized. Branch: `feat/issue-312`. Working directory created. Issue #312 linked in branch description."

### Example 3: Bug fix contribution

**User**: "I'm going to fix the install-plugin path bug, set up my branch"

**Extraction**: Fix type, description from context

**Action**:
```bash
aiwg contribute-start --type fix --description "install-plugin path bug"
```

**Response**: "Contribution initialized. Branch: `fix/install-plugin-path-bug`. DCO hook installed. Ready to commit."

## References

- @$AIWG_ROOT/src/cli/handlers/utilities.ts — Command handler
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference
- @$AIWG_ROOT/docs/contributing/ — Contribution guidelines

Related Skills

customize-contribute-back

104
from jmagly/aiwg

Contribute a user's AIWG customization back upstream as a PR — reviews for general applicability, creates branch, opens PR

intake-start

104
from jmagly/aiwg

Ingest the Project Intake Form and kick off Concept → Inception with agent assignments, accepts optional guidance to tailor process

Codex

intake-start-campaign

104
from jmagly/aiwg

Validate manually-created campaign intake forms and kick off Strategy phase with agent assignments

Codex

aiwg-orchestrate

104
from jmagly/aiwg

Route structured artifact work to AIWG workflows via MCP with zero parent context cost

venv-manager

104
from jmagly/aiwg

Create, manage, and validate Python virtual environments. Use for project isolation and dependency management.

pytest-runner

104
from jmagly/aiwg

Execute Python tests with pytest, supporting fixtures, markers, coverage, and parallel execution. Use for Python test automation.

vitest-runner

104
from jmagly/aiwg

Execute JavaScript/TypeScript tests with Vitest, supporting coverage, watch mode, and parallel execution. Use for JS/TS test automation.

eslint-checker

104
from jmagly/aiwg

Run ESLint for JavaScript/TypeScript code quality and style enforcement. Use for static analysis and auto-fixing.

repo-analyzer

104
from jmagly/aiwg

Analyze GitHub repositories for structure, documentation, dependencies, and contribution patterns. Use for codebase understanding and health assessment.

pr-reviewer

104
from jmagly/aiwg

Review GitHub pull requests for code quality, security, and best practices. Use for automated PR feedback and approval workflows.

YouTube Acquisition

104
from jmagly/aiwg

yt-dlp patterns for acquiring content from YouTube and video platforms

Quality Filtering

104
from jmagly/aiwg

Accept/reject logic and quality scoring heuristics for media content