setup-project

Project Setup

Automatically configure Claude Code for the current project. Supports monorepos with multiple languages in subdirectories.

Step 0: Resolve plugin root

The skill loader provides the base directory in the header: Base directory for this skill: <path>. Derive the plugin root from that:

PLUGIN_ROOT = <base directory>/../../

For example, if the skill base directory is ~/.claude/plugins/cache/pragma/skills/setup-project, then PLUGIN_ROOT is ~/.claude/plugins/cache/pragma.

Verify the plugin root is valid by checking for the plugin manifest:

PLUGIN_ROOT="<base directory>/../.."
[[ -f "$PLUGIN_ROOT/.claude-plugin/plugin.json" ]] && echo "OK" || echo "ERROR: Plugin root invalid - .claude-plugin/plugin.json not found at $PLUGIN_ROOT"
true

Note: Replace <base directory> with the actual path from the skill loader header above. For example, if the header says Base directory for this skill: /home/user/.claude/plugins/cache/pragma/skills/setup-project, then PLUGIN_ROOT="/home/user/.claude/plugins/cache/pragma/skills/setup-project/../..".

If the check fails, stop and show:

Plugin root could not be resolved. The pragma plugin may not be installed correctly.

Reinstall:
  /plugin marketplace add peteski22/agent-pragma
  /plugin install pragma@agent-pragma

STOP if check fails. Do not proceed.

Step 1: Detect project metadata

Get org and repo name from git remote:

git remote get-url origin 2>/dev/null | sed -E 's|.*[:/]([^/]+)/([^/]+)(\.git)?$|\1 \2|'

Store {org} and {repo} for templating.

Step 2: Scan for languages (root and subdirectories)

Check root directory and subdirectories (up to two levels deep) for language markers. Two-level scanning catches nested layouts like sdk/go/ or services/auth/.

# Root level
[[ -f go.mod ]] && echo "root:go"
( [[ -f pyproject.toml ]] || [[ -f setup.py ]] ) && echo "root:python"
[[ -f package.json ]] && echo "root:javascript"
[[ -f tsconfig.json ]] && echo "root:typescript"
[[ -f Cargo.toml ]] && echo "root:rust"

# Subdirectories (up to two levels deep, e.g. backend/ or sdk/python/).
# Prune heavy dirs so find never descends into them; skip the root marker
# (depth 1) since it's already covered by the root-level checks above.
find . -maxdepth 3 -type d \( -name node_modules -o -name .git -o -name vendor \) -prune -o \
  -type f \( -name go.mod -o -name pyproject.toml -o -name setup.py \
     -o -name package.json -o -name tsconfig.json -o -name Cargo.toml \) -print 2>/dev/null \
  | while IFS= read -r marker; do
  dir=$(dirname "$marker" | sed 's|^\./||')
  [ "$dir" = "." ] && continue
  case "$(basename "$marker")" in
    go.mod)          echo "${dir}:go" ;;
    pyproject.toml)  echo "${dir}:python" ;;
    setup.py)        echo "${dir}:python" ;;
    package.json)    echo "${dir}:javascript" ;;
    tsconfig.json)   echo "${dir}:typescript" ;;
    Cargo.toml)      echo "${dir}:rust" ;;
  esac
done | sort -u
true