me2resh/apexyard / .claude/skills/process
process
VerifiedExtract a business process from registered repos via 7-axis code scan + gap-targeted interview, then emit lint-clean BPMN 2.0.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 28.4 KB |
| cross-repo.shexecutable | script | 6.5 KB |
| discover.shexecutable | script | 16.7 KB |
| generate-bpmn.shexecutable | script | 13.9 KB |
| layout-bpmn.py | script | 7.5 KB |
| lint.shexecutable | script | 3.2 KB |
| tests/smoke.shexecutable | script | 12.0 KB |
| tests/test_bpmn_emit.shexecutable | script | 7.5 KB |
| tests/test_cross_repo.shexecutable | script | 4.8 KB |
| tests/test_process_bpmn.shexecutable | script | 7.9 KB |
lint.sh
View on GitHub#!/usr/bin/env bash
# /process lint.sh
#
# Run bpmnlint against a BPMN 2.0 file with the framework's default rules.
# Reads ${PROJECT_ROOT}/.bpmnlintrc when present to allow per-project overrides.
#
# Usage:
# lint.sh <output.bpmn> [--project-root=<dir>] [--max-warnings=0]
#
# Exit codes:
# 0 — clean (no errors, no warnings above --max-warnings)
# 1 — violations exist (run interactively to see them)
# 2 — bad input
# 3 — bpmnlint / npx not available (Node missing)
set -euo pipefail
FILE=""
PROJECT_ROOT=""
MAX_WARNINGS=0
while [ $# -gt 0 ]; do
case "$1" in
--project-root=*) PROJECT_ROOT="${1#--project-root=}"; shift ;;
--max-warnings=*) MAX_WARNINGS="${1#--max-warnings=}"; shift ;;
--help|-h)
sed -n '2,18p' "$0"
exit 0
;;
-*)
echo "lint.sh: unknown flag: $1" >&2
exit 2
;;
*)
if [ -z "$FILE" ]; then
FILE="$1"
else
echo "lint.sh: unexpected positional arg: $1" >&2
exit 2
fi
shift
;;
esac
done
if [ -z "$FILE" ]; then
echo "lint.sh: BPMN file path is required" >&2
exit 2
fi
if [ ! -f "$FILE" ]; then
echo "lint.sh: file not found: $FILE" >&2
exit 2
fi
if ! command -v npx >/dev/null 2>&1; then
cat >&2 <<MSG
lint.sh: npx not found — bpmnlint cannot run.
Install Node + npm (https://nodejs.org), then re-run /process.
To skip the lint gate, pass --skip-lint to the parent skill (the operator
owns the consequences — a non-lint-clean BPMN may render badly in
Camunda Modeler).
MSG
exit 3
fi
# ---------------------------------------------------------------------------
# Resolve the .bpmnlintrc to use.
# 1. Use ${PROJECT_ROOT}/.bpmnlintrc if it exists.
# 2. Else write a tempfile with framework defaults and use that.
# ---------------------------------------------------------------------------
WORK=$(mktemp -d -t process-lint-XXXXXX)
trap 'rm -rf "$WORK"' EXIT
RC="$WORK/.bpmnlintrc"
if [ -n "$PROJECT_ROOT" ] && [ -f "$PROJECT_ROOT/.bpmnlintrc" ]; then
cp "$PROJECT_ROOT/.bpmnlintrc" "$RC"
else
cat > "$RC" <<'JSON'
{
"extends": "bpmnlint:recommended",
"rules": {
"label-required": "error",
"no-disconnected": "error",
"no-implicit-split": "warn"
}
}
JSON
fi
# Run bpmnlint. Cache the npx package via -y so prompts are skipped.
# bpmnlint exits 0 on clean, 1 on violations, other on internal errors.
set +e
npx -y bpmnlint --config "$RC" "$FILE" > "$WORK/out.txt" 2>&1
RC_EXIT=$?
set -e
# Always print bpmnlint's output (whether it found issues or not).
cat "$WORK/out.txt"
# Parse the actual summary, including singular error/warning counts.
# Missing summaries (for example, npm failures) never turn a failed run clean.
SUMMARY=$(sed -nE 's/.* ([0-9]+) problems? \(([0-9]+) errors?, ([0-9]+) warnings?\).*/\2 \3/p' "$WORK/out.txt" | tail -1)
ERRORS=0
WARNS=0
if [ -n "$SUMMARY" ]; then
read -r ERRORS WARNS <<< "$SUMMARY"
fi
if [ "$RC_EXIT" -ne 0 ] || [ "$ERRORS" -gt 0 ]; then
echo "lint.sh: bpmnlint failed (exit $RC_EXIT, $ERRORS error(s), $WARNS warning(s))" >&2
exit 1
fi
if [ "$WARNS" -gt "$MAX_WARNINGS" ]; then
echo "lint.sh: $WARNS warning(s) exceeds --max-warnings=$MAX_WARNINGS" >&2
exit 1
fi
echo "lint.sh: bpmnlint clean (warnings within threshold)"
exit 0
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |