Reads graphify-out/graph.json and appends a timestamped knowledge snapshot to KNOWLEDGESUMMARY.md in the project root. Entries are always appended, never overwritten — building a chronological evidence log of knowledge graph states. Use after /graphify-monitor has built a graph to record what the graph currently knows.
Installs graphify, builds an initial knowledge graph of the current project, then spawns a background subagent that runs graphify auto-update every 120 seconds and prints newly-discovered symbols to the terminal. Use when monitoring a project for structural changes during active development by another coding agent.…
Interactive git rebase conflict resolver with Dry-run, Progressive, and Auto modes. Dry-run predicts conflict paths without touching the branch. Progressive mode is interactive per-conflict. Auto mode resolves autonomously then presents an audit report for approval or rollback. All modes generate a report. Use when…
Scans remote origin branches behind the base branch, filters by staleness threshold, generates a per-branch scan report with intent analysis and Jira detection, then optionally deletes remote branches and prunes local counterparts. Dry-run mode reports without deleting. Use when cleaning up stale branches, pruning old…
Interactive multi-select installer for external agent skill registries. Reads project-config.md to derive best-fit skills for the project, fetches latest version info from GitHub, and installs selected skills via npx. Supports supabase/agent-skills, vercel-labs/agent-skills, and antonbabenko/terraform-skill. Use when…
Create an Azure DevOps pull request for the current branch using the Azure DevOps MCP. Pushes the branch, generates the description via the generate-pr-notes contract, opens the PR against a target branch (default develop), and adds reviewers resolved from teams or explicit emails. By default (opt out with…
Read active review comments on an Azure DevOps PR and resolve them by applying the suggested fixes with user consent. Trivial fixes are shown as before/after diffs for quick approval. Non-trivial changes produce a refactoring plan for user review before execution. Companion to ado-pr-code-review. Use when asked to…
Automatically generate pull request notes based on git changes. Analyzes commits or branch diffs and creates comprehensive PR descriptions with a title, summary, changes, technical details, and breaking changes. Use when creating a PR, writing PR description, summarizing changes for review, or asked to generate PR…
Strict Conventional Commits generator optimized for git-cliff, with SemVer and Emoji support. Use when committing code changes, writing commit messages, or when asked to commit with conventional format, semantic versioning, emoji commits, or gitmoji.
Install and configure the Atlassian MCP server (Jira and Confluence) for Claude or GitHub Copilot agents. Supports uvx (recommended) and Docker methods. Use when setting up Atlassian MCP, Jira MCP, Confluence MCP, or asked to install atlassian mcp.
Install and configure the Azure DevOps MCP server for Claude or GitHub Copilot agents. Use when setting up Azure DevOps MCP, ADO MCP, work items, repos, pipelines, sprints, wikis, or asked to install azure devops mcp.
Install and configure the Playwright browser-automation MCP server for Claude or GitHub Copilot agents. Use when setting up Playwright MCP, browser automation, web testing tools, or asked to install playwright mcp.
Install and configure the official Sentry MCP server for Claude or GitHub Copilot agents. Supports remote (OAuth, recommended) and local stdio (npx + access token) methods. Use when setting up Sentry MCP, error-monitoring MCP, Seer, or asked to install sentry mcp.
One-time setup skill that generates .agent-settings/project-config.md — a namespaced per-MCP project-settings file. Scans the codebase for structure, discovers installed MCPs from .mcp.json, and prompts for each MCP's project-scoped (non-secret) fields plus the SDD tool. Credentials stay in the global /.env.mcp…
Recalibrate a repo's spec-driven docs against the code that now implements them. Sweeps every source-of-truth spec (spec-kit specs/, openspec openspec/specs/), maps each to its code, classifies drift, and with consent updates stale spec docs to match the code — spec docs only, never the code implementation — recording…
Interactively guides the user to select a target git worktree, then symlinks all git-ignored files and directories from the current worktree to the target. Use when setting up a new worktree, sharing .env files across worktrees, or asked to symlink ignored files to another worktree.
Scans all API routes in the project and maintains docs/agents/api-spec.md — a machine-readable API reference for coding agents, frontend, and product to understand what APIs do. Incremental: only re-scans handlers for new or changed routes. Optional Confluence publish step after local file is written. Use at the…
Sync the local .agents/skills directory with the ClawHub registry. Detects which skills are not yet installed and installs them automatically. Use whenever you want to pull down new or missing skills from the registry without reinstalling ones that are already present. Triggers on: "install new skills", "sync skills"…
General-purpose goal tracking with automatic checkpoint/resume support. Commits current state and writes a GOALSTATE.md snapshot when context usage approaches 90%, ensuring the next session can fully restore and continue the work.
Fetches an external PRD from Confluence or from a Jira ticket that links to a PRD wiki, and transforms it into a structured local source file that the RD can reference when running SDD tools like spec-kit specify or openspec. Bridges the PO handoff into the SDD workflow.
Reads local spec-kit artifacts and derives BDD QA scenarios, then creates QA sub-tickets under the existing root Jira ticket from Phase 7. Use this as the explicit QA hand-off after a PR is created in the spec-kit native SDD workflow.
Reads local SDD artifacts (from spec-kit, openspec, or similar tools) and derives BDD QA scenarios, then creates QA sub-tickets under the existing root Jira ticket from Phase 7. Use this as the explicit QA hand-off after a PR is created in the SDD workflow.