github-installation

Stars6

Forks0

UpdatedMay 12, 2026 at 12:07

Handle GitHub App installation lifecycle webhooks (installation created, deleted, repositories added/removed). Records the change so the integrations UI can react. The github plugin's other webhooks (issues, pulls) should trigger their own skills as the migration progresses.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

Zuttam

Zuttam/hissuno

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	github-installation
description	Handle GitHub App installation lifecycle webhooks (installation created, deleted, repositories added/removed). Records the change so the integrations UI can react. The github plugin's other webhooks (issues, pulls) should trigger their own skills as the migration progresses.
version	1.0
license	MIT
metadata	{"author":"hissuno"}
triggers	{"events":["webhook.github"]}
capabilities	{"sandbox":true,"webSearch":false}
requires	{"plugins":["github"]}
timeoutMs	300000

GitHub Webhooks

Fires for every GitHub webhook delivered to /api/webhooks/github after the plugin's resolveConnection matches the installation to a hissuno connection.

Migration status

Currently a placeholder. Issue/PR-driven sync still requires the github-feedback and github-codebase skills to be migrated and triggered. This skill exists so that installation events route somewhere meaningful.

Inputs

{
  "pluginId": "github",
  "connectionId": "<uuid>",
  "externalAccountId": "<installation-id>",
  "payload": { ...github webhook payload... }
}

What to do

Record a short summary to output.json describing the event action and target. Do not call the GitHub API directly here — installation events don't need it.

tsx scripts/sync.ts

More from this repository

same repository

fathom-meetings

Zuttam/hissuno

Sync Fathom meetings (recorded calls + transcripts) into Hissuno as sessions. Cursor advances by `created_at`.

2026-05-126

github-codebase

Zuttam/hissuno

Register a GitHub repository as a Hissuno codebase. Parameterized: pass `repoFullName` and optional `branch`. Verifies the repo (and branch, if provided) is reachable, then POSTs to /api/codebases. Re-running is idempotent — duplicate codebases on the same (project, repo, branch) are filtered server-side.

2026-05-126

github-feedback

Zuttam/hissuno

Sync GitHub issues from a repository as feedback sessions. Parameterized: pass `repoFullName` (owner/repo) as run input. Cursor advances by issue `updated_at`. Pulls comments inline so each session has the full thread.

2026-05-126

gong-calls

Zuttam/hissuno

Sync Gong calls (recorded sales calls + transcripts) into Hissuno as sessions. Cursor advances by call started date.

2026-05-126

hissuno-continuous-dev

Zuttam/hissuno

Use when picking the next development issue to work on and implementing it end-to-end. This skill is the body of a continuous development loop - it selects the highest-priority ready issue from Hissuno, implements it, and creates a PR. Triggers on: next issue, continuous development, dev loop, what to build next, pick next task, implement next issue, development queue. Requires the hissuno CLI to be configured.

2026-05-126

hissuno-customer-health

Zuttam/hissuno

Use when analyzing a customer account - understanding their feedback history, open issues, contact activity, sentiment trajectory, and overall health. Triggers on: customer health, account review, customer deep dive, account analysis, churn risk, customer assessment, renewal prep, account health check. Requires the hissuno CLI to be configured.

2026-05-126

name	github-installation
description	Handle GitHub App installation lifecycle webhooks (installation created, deleted, repositories added/removed). Records the change so the integrations UI can react. The github plugin's other webhooks (issues, pulls) should trigger their own skills as the migration progresses.
version	1.0
license	MIT
metadata	{"author":"hissuno"}
triggers	{"events":["webhook.github"]}
capabilities	{"sandbox":true,"webSearch":false}
requires	{"plugins":["github"]}
timeoutMs	300000

GitHub Webhooks

Fires for every GitHub webhook delivered to /api/webhooks/github after the plugin's resolveConnection matches the installation to a hissuno connection.

Migration status

Inputs

{
  "pluginId": "github",
  "connectionId": "<uuid>",
  "externalAccountId": "<installation-id>",
  "payload": { ...github webhook payload... }
}

What to do

Record a short summary to output.json describing the event action and target. Do not call the GitHub API directly here — installation events don't need it.

tsx scripts/sync.ts