# contribute-to-org

> Contribute team discoveries (skills, knowledge, framework fixes) to parent organization repository

- Author: Andrew Holder
- Repository: drewswiredin/vincent-chappie
- Version: 20260209202943
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-10
- Source: https://github.com/drewswiredin/vincent-chappie
- Web: https://mule.run/skillshub/@@drewswiredin/vincent-chappie~contribute-to-org:20260209202943

---

---
skill: contribute-to-org
description: Contribute team discoveries (skills, knowledge, framework fixes) to parent organization repository
domain: orchestrator
created: 2026-02-09
---

# Contribute to Organization

Copies files or directories from this team repository to the parent organization repository for review and integration.

**Level**: Team repositories only (validates `.chappie-config` level is `team`)

## What This Skill Does

1. Accepts file/directory path as argument
2. Validates this repository is team level
3. Validates contribution is org-relevant (not team-specific)
4. Copies file/directory to org working copy
5. Outputs instructions for org maintainer to review and commit

## What Can Be Contributed

**Allowed contributions:**

- ✓ **Org skills**: `.claude/skills/org-*/` - Skills useful across entire organization
- ✓ **Org knowledge**: `docs/environment/org/` - Organization-wide documentation
- ✓ **Framework fixes**: `hooks/`, `scripts/`, `.claude/skills/orchestrator-*/` - Bug fixes or improvements
- ✓ **Seed agent fixes**: `.claude/agents/github.md`, `.claude/agents/docs.md`
- ✓ **Framework docs**: `docs/architecture/`, `docs/claude-operations/`
- ✓ **Runbooks**: `docs/runbooks/` - Operational procedures valuable org-wide

**Blocked contributions:**

- ✗ **Team knowledge**: `docs/environment/teams/` - Team-specific documentation
- ✗ **Team skills**: `.claude/skills/team-*/` - Team domain skills
- ✗ **Team roadmaps/plans**: Team-specific work artifacts
- ✗ **Team brainstorms**: Team conversation artifacts

## Usage

```bash
/contribute-to-org <file-or-directory>
```

**Arguments:**
- `<file-or-directory>`: Path to file or directory to contribute (relative or absolute)

**Examples:**

```bash
# Contribute an org skill
/contribute-to-org .claude/skills/org-kubernetes-deployment/

# Contribute org knowledge
/contribute-to-org docs/environment/org/inventory/new-service.md

# Contribute a framework fix
/contribute-to-org hooks/SessionStart.sh

# Contribute a runbook
/contribute-to-org docs/runbooks/database-backup.md
```

## Prerequisites

1. `.chappie-config` must exist with:
   - `level: team`
   - `parent.level: organization`
   - `parent.path: /absolute/path/to/org-chappie`

2. Parent organization repository must be accessible at the specified path

3. File/directory to contribute must exist in current repository

## Algorithm

1. **Validate configuration**
   - Run `scripts/validate-chappie-config.sh`
   - Confirm level is `team`
   - Extract parent org path

2. **Validate contribution**
   - Check file/directory exists
   - Verify path is org-relevant (not team-specific)
   - Check for org-specific naming conventions

3. **Copy to org repository**
   - Use `cp -r` to copy file/directory to parent
   - Preserve permissions and timestamps
   - Report copy status

4. **Output instructions**
   - Print org maintainer instructions
   - Include git commands for review and commit
   - Provide context about what was contributed

## Implementation

Use bash script for validation and copying:

```bash
#!/usr/bin/env bash
set -euo pipefail

# 1. Check arguments
if [[ $# -ne 1 ]]; then
    echo "Usage: /contribute-to-org <file-or-directory>"
    exit 1
fi

CONTRIBUTION_PATH="$1"

# 2. Validate config
bash scripts/validate-chappie-config.sh

# 3. Parse config
LEVEL=$(awk '$1 == "level:" { print $2 }' .chappie-config)
PARENT_PATH=$(awk '/parent:/{flag=1; next} flag && /path:/{print $2; exit}' .chappie-config)

# 4. Validate level
if [[ "$LEVEL" != "team" ]]; then
    echo "ERROR: This skill is only for team-level repositories (current level: $LEVEL)"
    exit 1
fi

# 5. Check parent exists
if [[ ! -d "$PARENT_PATH" ]]; then
    echo "ERROR: Parent organization path not found: $PARENT_PATH"
    exit 1
fi

# 6. Check contribution exists
if [[ ! -e "$CONTRIBUTION_PATH" ]]; then
    echo "ERROR: File or directory not found: $CONTRIBUTION_PATH"
    exit 1
fi

# 7. Validate contribution is org-relevant (not team-specific)
BLOCKED_PATTERNS=(
    "docs/environment/teams/"
    ".claude/skills/team-"
)

for pattern in "${BLOCKED_PATTERNS[@]}"; do
    if [[ "$CONTRIBUTION_PATH" == *"$pattern"* ]]; then
        echo "ERROR: Cannot contribute team-specific content to organization: $CONTRIBUTION_PATH"
        echo "Blocked pattern: $pattern"
        echo ""
        echo "Team-specific knowledge and skills should stay at team level."
        echo "Only org-wide content (org skills, org knowledge, framework fixes) can be contributed."
        exit 1
    fi
done

# 8. Copy to parent
echo "Copying to organization repository..."
cp -r "$CONTRIBUTION_PATH" "$PARENT_PATH/$CONTRIBUTION_PATH"

echo ""
echo "✓ Contribution copied to organization repository!"
echo ""
echo "Copied: $CONTRIBUTION_PATH"
echo "To: $PARENT_PATH/$CONTRIBUTION_PATH"
echo ""
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
echo "ORG MAINTAINER: Review and commit the contribution"
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
echo ""
echo "1. Review changes:"
echo "   cd $PARENT_PATH"
echo "   git status"
echo "   git diff"
echo ""
echo "2. If approved, commit:"
echo "   git add $CONTRIBUTION_PATH"
echo "   git commit -m 'Add contribution from team: $CONTRIBUTION_PATH'"
echo ""
echo "3. Push to org remote:"
echo "   git push origin main"
echo ""
echo "4. If this is a framework fix, consider contributing upstream:"
echo "   git push origin fix-branch"
echo "   # Then create PR on GitHub: yourorg/chappie-org → upstream/chappie"
echo ""
echo "5. Other teams will receive this on next sync:"
echo "   /sync-from-org"
echo ""
```

## Contribution Review Checklist (Org Maintainer)

When reviewing contributions from teams:

1. **Verify org-wide relevance**
   - Useful across multiple teams (not just one team)
   - Fits organization's domain and scope
   - Doesn't duplicate existing org skills/knowledge

2. **Check quality**
   - Code follows org conventions
   - Documentation is clear and complete
   - Skill has proper frontmatter and structure

3. **Validate security**
   - No hardcoded secrets or credentials
   - No team-specific information exposed
   - Paths are generic (not team-specific)

4. **Test functionality**
   - Run skill to verify it works
   - Check for dependencies
   - Ensure portable across all teams

5. **Consider upstream contribution**
   - Is this a framework improvement worth contributing to source?
   - Does it fix a bug in the base framework?
   - Would other organizations benefit?

6. **Update registries** (if needed)
   - Add skill to skills-registry.md
   - Update mkdocs navigation for docs
   - Run consistency validation

## Upstream Contribution Workflow (Org → Source)

For framework fixes that should go upstream:

1. **Commit to org repo** (as shown above)

2. **Create feature branch**
   ```bash
   cd /path/to/org-chappie
   git checkout -b fix/reconciliation-hook
   ```

3. **Push to org remote**
   ```bash
   git push origin fix/reconciliation-hook
   ```

4. **Create GitHub PR**
   - Go to: https://github.com/yourorg/chappie-org
   - Click "New Pull Request"
   - Base: `upstream/chappie:main`
   - Compare: `yourorg/chappie-org:fix/reconciliation-hook`
   - Describe the fix and why it benefits all organizations

## Error Handling

**No .chappie-config:**
- Error: "Configuration file not found. Is this a four-tier CHAPPiE repository?"
- Solution: Create `.chappie-config` or use deployment script

**Wrong level:**
- Error: "This skill is only for team-level repositories (current level: X)"
- Solution: Use `/contribute-to-team` for instance level

**Blocked contribution:**
- Error: "Cannot contribute team-specific content to organization: <path>"
- Solution: Team knowledge and skills stay at team level

**Parent path missing:**
- Error: "Parent organization path not found: /path/to/org"
- Solution: Update `.chappie-config` with correct parent path

**File not found:**
- Error: "File or directory not found: <path>"
- Solution: Check path spelling, ensure file exists

## Related Skills

- `/contribute-to-team` - Contribute instance discoveries to team level
- `/sync-from-org` - Sync latest org knowledge to this team
- `scripts/validate-chappie-config.sh` - Validate configuration structure

## See Also

- [repository-sync-strategy.md](../../../docs/environment/brainstorms/four-tier-chappie-architecture/repository-sync-strategy.md) - Complete sync strategy documentation
- [four-tier-architecture/index.md](../../../docs/environment/brainstorms/four-tier-chappie-architecture/index.md) - Architecture overview