Github Pr Issue Automation

GitHub PR & Issue Visual Automation Skill

This skill defines the official standards for authoring visually striking, professional, and automated Pull Requests and Issues on GitHub, and operating the automated triage and label synchronization system.

1. Automated GitHub Actions Triage Pipeline

When any PR or issue is opened, the GitHub Actions triage automation executes automatically:

1. Auto-Assignee:
   • Assigns the Pull Request or Issue to the author (or repository owner @MishraShardendu22) immediately upon creation.
2. Conventional Type Labeling:
   • Inspects the PR title prefix (feat:, fix:, perf:, refactor:, docs:, db:, ci:, test:, ui:) and automatically applies the matching color-coded type/* label.
3. Subsystem / Area Labeling:
   • Inspects modified files in the pull request:
     • frontend/** $\rightarrow$ area/frontend
     • backend/** $\rightarrow$ area/backend
     • agentic-observatory/** $\rightarrow$ area/observatory
     • backup-worker/** $\rightarrow$ area/backup-worker
     • .github/**, scripts/**, Makefile $\rightarrow$ area/ci-cd
     • docs/**, .agents/skills/** $\rightarrow$ area/documentation
4. Automated Diff Size Classification:
   • Computes total lines changed:
     • < 50 lines $\rightarrow$ size/XS
     • < 250 lines $\rightarrow$ size/S
     • < 500 lines $\rightarrow$ size/M
     • < 1000 lines $\rightarrow$ size/L
     • 1000+ lines $\rightarrow$ size/XL
5. Lifecycle Status:
   • Non-draft PRs receive status/ready-for-review; drafts receive status/in-progress.

2. CLI Standards for Agents: Opening Pull Requests

When instructed to open a Pull Request, agents must use gh pr create with explicit parameters:

gh pr create \
  --base main \
  --head <github-username>/<parent-branch>/<feature> \
  --title "<type>(<scope>): <concise imperative summary>" \
  --assignee "@me" \
  --label "type/<type>,area/<subsystem>,status/ready-for-review" \
  --body "..."

Visual Formatting Checklist for PR Bodies

Every PR description generated by agents MUST include:

• Executive Summary: 2-3 concise sentences explaining the problem and resolution.
• Conventional Type Checkbox: Explicitly mark the type of change.
• Subsystem Impact Table: Markdown table displaying all affected services.
• Quality Assurance Checklist: Showing exact test commands executed (make test, make pre-commit).
• Security Certification: Affirming zero secrets or tokens committed.

3. Label Synchronization Engine: make labels-sync

To synchronize or update the repository's 26 color-coded labels, run:

# Preview labels without changes
./scripts/github-labels-sync.sh --dry-run

# Synchronize labels to GitHub
./scripts/github-labels-sync.sh

# Makefile target
make labels-sync

4. Modern Issue Forms

Issues are created through standardized YAML issue forms in .github/ISSUE_TEMPLATE/:

• bug_report.yml: Structured bug reproduction steps, environment, logs.
• feature_request.yml: Problem statement, target subsystem, architecture proposal.
• task.yml: Engineering task, acceptance criteria, test commands.