forge-core

Data analyst — success metrics, KPIs, measurement strategies, business impact analysis, data-driven evaluation. USE WHEN metrics design, success criteria, impact analysis, data strategy.

Documentation specialist — README quality, API docs, developer experience, onboarding clarity. USE WHEN documentation review, README evaluation, developer experience assessment, onboarding analysis.

Forensic security analyst — PII detection, secret scanning, identity leak auditing across git history, staged changes, working tree, all branches, and cross-repo GitHub-wide audits. USE WHEN PII scan, leaked name, pre-publication audit, git history audit, secret scan, security review, forensic analysis, scan my github.

Product manager — requirements clarity, user goals, roadmap alignment, market fit, prioritization trade-offs. USE WHEN requirements review, feature scoping, roadmap decisions, product strategy.

Provenance and deployment integrity auditor -- validates SLSA sidecars, manifests, and drift across providers. USE WHEN check provenance, audit deployment, verify integrity, detect drift, stale files, manifest check.

Decompose a research question into sub-queries, spawn parallel WebResearcher agents per angle, synthesize findings with citations and explicit confidence. USE WHEN the user asks to research, investigate, look online, look up, dig into, find sources, gather evidence, or survey what's known about a topic. Single-pass; for multi-round adversarial research use ResearchCouncil in forge-council.

Commit-time secret scanning with gitleaks — prevent credentials from entering git history. USE WHEN scanning for leaked secrets, setting up pre-commit hooks, auditing repositories for credentials, configuring gitleaks allowlists, or encrypting user-specific module data with git-crypt.

Explain the intent behind source code by tracing it to the agent session transcript that created it. USE WHEN why does this function exist, what is this file for, why was this line added, explain this code's history, trace code to its originating conversation.

Continue work from another agent's session — auto-detect the most relevant saved session, read its transcript, summarize, and pick up the work. USE WHEN continue from another agent, hand off a session, pick up where codex or gemini left off, summarize a saved session or checkpoint, inspect recent sessions. Not for searching old work by topic — use SessionSearch for that.

Search past agent sessions and checkpoints — semantic + keyword recall across repos, branches, authors, and time windows. USE WHEN have we done this before, search past work, find the previous implementation, look for checkpoints about X, recover a prior prompt. Not for the current active session — use SessionHandoff for that.

5 hooks across 2 events