# contribute-to-team

> Contribute instance discoveries (skills, knowledge) to parent team 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-team:20260209202943

---

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

# Contribute to Team

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

**Level**: Instance repositories only (validates `.chappie-config` level is `instance`)

## What This Skill Does

1. Accepts file/directory path as argument
2. Validates this repository is instance level
3. Validates contribution is allowed (not personal roadmaps/plans)
4. Copies file/directory to team working copy
5. Outputs instructions for team maintainer to review and commit

## What Can Be Contributed

**Allowed contributions:**

- ✓ **Team skills**: `.claude/skills/team-*/` - Skills useful for the entire team
- ✓ **Team knowledge**: `docs/environment/teams/[team-name]/` - Team-specific documentation
- ✓ **Framework fixes**: `hooks/`, `scripts/`, `.claude/skills/orchestrator-*/` - Bug fixes or improvements to framework
- ✓ **Seed agent fixes**: `.claude/agents/github.md`, `.claude/agents/docs.md`
- ✓ **Runbooks**: `docs/runbooks/` - Operational procedures valuable to team

**Blocked contributions:**

- ✗ **Personal roadmaps**: `docs/environment/roadmaps/` - Strategic work artifacts
- ✗ **Personal plans**: `docs/environment/plans/` - Tactical work artifacts
- ✗ **Personal brainstorms**: `docs/environment/brainstorms/` - Conversation artifacts
- ✗ **Member knowledge**: `docs/environment/members/` - Personal knowledge base
- ✗ **Personal scratch notes**: `MEMORY.local.md`

## Usage

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

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

**Examples:**

```bash
# Contribute a team skill
/contribute-to-team .claude/skills/team-alpha-deploy-automation/

# Contribute team knowledge
/contribute-to-team docs/environment/teams/team-alpha/conventions.md

# Contribute a framework fix
/contribute-to-team hooks/PostToolUse.sh

# Contribute a runbook
/contribute-to-team docs/runbooks/k8s-deployment.md
```

## Prerequisites

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

2. Parent team 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 `instance`
   - Extract parent team path

2. **Validate contribution**
   - Check file/directory exists
   - Verify path is allowed (not personal roadmaps/plans)
   - Check for team-specific naming conventions

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

4. **Output instructions**
   - Print team 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-team <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" != "instance" ]]; then
    echo "ERROR: This skill is only for instance-level repositories (current level: $LEVEL)"
    exit 1
fi

# 5. Check parent exists
if [[ ! -d "$PARENT_PATH" ]]; then
    echo "ERROR: Parent team 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 allowed
BLOCKED_PATTERNS=(
    "docs/environment/roadmaps/"
    "docs/environment/plans/"
    "docs/environment/brainstorms/"
    "docs/environment/members/"
    "MEMORY.local.md"
)

for pattern in "${BLOCKED_PATTERNS[@]}"; do
    if [[ "$CONTRIBUTION_PATH" == *"$pattern"* ]]; then
        echo "ERROR: Cannot contribute personal work artifacts: $CONTRIBUTION_PATH"
        echo "Blocked pattern: $pattern"
        echo ""
        echo "Personal roadmaps, plans, brainstorms, and member knowledge cannot be contributed to team."
        exit 1
    fi
done

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

echo ""
echo "✓ Contribution copied to team repository!"
echo ""
echo "Copied: $CONTRIBUTION_PATH"
echo "To: $PARENT_PATH/$CONTRIBUTION_PATH"
echo ""
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
echo "TEAM 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 instance: $CONTRIBUTION_PATH'"
echo ""
echo "3. Push to team remote:"
echo "   git push"
echo ""
echo "4. Other team members will receive this on next sync:"
echo "   /sync-from-team"
echo ""
```

## Contribution Review Checklist (Team Maintainer)

When reviewing contributions from instances:

1. **Verify quality**
   - Code follows team conventions
   - Documentation is clear and complete
   - Skill has proper frontmatter and structure

2. **Check relevance**
   - Useful for entire team (not just one person)
   - Fits team's domain and scope
   - Doesn't duplicate existing skills/knowledge

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

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

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

## 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 instance-level repositories (current level: X)"
- Solution: Use `/contribute-to-org` for team level

**Blocked contribution:**
- Error: "Cannot contribute personal work artifacts: <path>"
- Solution: Personal roadmaps/plans/brainstorms stay at instance level

**Parent path missing:**
- Error: "Parent team path not found: /path/to/team"
- 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-org` - Contribute team discoveries to organization level
- `/sync-from-team` - Sync latest team knowledge to this instance
- `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