plugins/gh-workflow/skills/repo-config/SKILL.md
Provides dynamic repository configuration patterns for gh-workflow agents. Use when an agent needs the default branch name for diffs, the repository owner/name for API calls, or branch naming and commit conventions for validation.
npx skillsauth add synaptiai/synapti-marketplace repo-configInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Reference skill loaded into agent context via skills: repo-config. Provides patterns for dynamic repository detection so agents never hardcode branch names, repo identifiers, or conventions.
Used by code-reviewer for diff base and convention-checker for commit range:
DEFAULT_BRANCH=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')
# Usage in agents:
git diff origin/$DEFAULT_BRANCH..HEAD # code-reviewer
git log --oneline $DEFAULT_BRANCH..HEAD # convention-checker
Used by implementation-planner for GitHub API calls:
REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')
# Usage in agents:
gh api repos/$REPO/issues/$ISSUE_NUMBER/comments
gh api repos/$REPO/pulls/$PR_NUMBER/comments
When multiple values are needed, minimize API calls:
gh repo view --json nameWithOwner,defaultBranchRef --jq '{
repo: .nameWithOwner,
default_branch: .defaultBranchRef.name
}'
Used by convention-checker to validate branch names and commit messages. These defaults are configurable via settings.gh-workflow.json (see conventions.* keys in schema.json). Commands may also override with project-specific conventions from CLAUDE.md — check CLAUDE.md first, then settings, then these defaults.
Configurable via .conventions.branchPatterns and .conventions.additionalBranchTypes in settings.
| Type | Default Pattern | Example |
|------|----------------|---------|
| Feature | feature/issue-{N}-{desc} | feature/issue-42-add-login |
| Fix | fix/issue-{N}-{desc} | fix/issue-13-typo |
| Docs | docs/issue-{N}-{desc} | docs/issue-7-readme |
Additional branch types can be added via .conventions.additionalBranchTypes (e.g., {"refactor": "refactor/issue-{N}-{desc}", "chore": "chore/issue-{N}-{desc}"}).
Configurable via .conventions.commitTypes in settings.
| Prefix | Usage |
|--------|-------|
| feat: | New features |
| fix: | Bug fixes |
| docs: | Documentation |
| refactor: | Code refactoring |
| test: | Test changes |
| chore: | Maintenance |
# Check CLAUDE.md first (preferred source)
CLAUDE_MD=""
[ -f ".claude/CLAUDE.md" ] && CLAUDE_MD=".claude/CLAUDE.md"
[ -z "$CLAUDE_MD" ] && [ -f "CLAUDE.md" ] && CLAUDE_MD="CLAUDE.md"
[ -n "$CLAUDE_MD" ] && grep -A5 -E "(Branch|Commit|Convention)" "$CLAUDE_MD" 2>/dev/null
# Fall back to inferring from existing patterns
git for-each-ref --sort=-committerdate --format='%(refname:short)' refs/remotes/origin/ | head -10
git log --oneline -20
This skill is loaded into agent context via skills: repo-config in agent frontmatter:
| Agent | What it needs | Key commands |
|-------|--------------|--------------|
| code-reviewer | DEFAULT_BRANCH for diff base | git diff origin/$DEFAULT_BRANCH..HEAD |
| convention-checker | DEFAULT_BRANCH for commit range, conventions for validation | git log $DEFAULT_BRANCH..HEAD, branch/commit patterns |
| implementation-planner | REPO for GitHub API calls | gh api repos/$REPO/issues/... |
| test-runner | Declared but not directly used | — |
If gh commands fail:
| Check | Command | Fix |
|-------|---------|-----|
| Authentication | gh auth status | Run gh auth login |
| Git repository | git rev-parse --git-dir | Navigate to a git repo or run git init |
| GitHub remote | git remote -v | Add with git remote add origin <url> |
tools
Validate a FlowWorkflow YAML at `plugins/flow/workflows/<id>.workflow.yaml` against `schemas/v1/workflow.schema.json` AND cross-reference the referenced skills/agents exist + every Tier 3 action is confirm-gated + no native /goal or /loop dependency is declared. Use when /flow:workflow validate is invoked, when CI runs the workflow schema gates, or when a new workflow is being authored. This skill MUST be consulted because schema validation alone catches shape errors; cross-reference validation catches the silent-correctness failures (typo'd skill name, Tier 3 escape, /goal dependency) that would otherwise ship to users.
tools
Verify UI-facing changes by running a screenshot-analyze-verify loop across configured viewports, with a browser-tool priority cascade (Playwright MCP → Chrome DevTools MCP → CLI fallback → external skill fallback) and bounded iteration. Use after build/runtime verification passes and the diff includes `.tsx`/`.jsx`/`.vue`/`.html`/`.css`/`.scss`/`.svelte` files OR the acceptance criteria mention UI/page/render/display/visual. This skill MUST be consulted because UI changes that pass build and unit tests can still ship blank pages, render-blocking console errors, or broken responsive layouts that no other verification phase catches.
data-ai
Coordinate agent teams for adversarial review (paired skeptic/verifier per facet, challenge round with disposition vocabulary, consolidated findings with confidence) or parallel implementation (task sizing 5-6 per teammate, non-overlapping files). Enforces independent analysis before shared conclusions. Reference only (`disable-model-invocation: true`); loaded only when `agentTeams: true` in settings.
development
Conduct two-stage code review: Stage 1 verifies spec compliance (criterion-to-code mapping), Stage 2 evaluates security, correctness, performance, and maintainability across 6 parallel facets with P1/P2/P3 synthesis and deduplication by file:line. Use when reviewing code changes or pull requests. This skill MUST be consulted because reviewing quality on broken logic is wasted effort, and unmet acceptance criteria must block merge.