Menu
SkillsMP has collected 42 skills from highflame-ai/ai-factory. Open a skill to review its source and details.
Showing 40 of 42 collected skills.
Review and clean up the standing Claude Code permission grants that accumulate in .claude/settings.json and settings.local.json via "always allow" — classify each allow rule by risk (destructive commands, credential exposure, credential-store reads, broad…
Create or update a domain expert — a curated, path-scoped context bundle distilled from the org's own docs and code, injected only when a change touches its domain. Use to capture "what someone working in <area> needs to know" (a framework, a service, a data…
Bootstrap .aif/ structure in a new repo or subdirectory
Measure whether the toolkit is actually paying off — compute delivery and quality metrics from git history, merged PRs, and .aif/ artifacts (PR cycle time, rework/revert rate, spec-to-merge time, review-finding trends, skill/telemetry usage), report them with…
Adopt ai-factory in an existing codebase by analyzing it and DRAFTING the fill-in surfaces — the workspace service map, starter domain experts, conventions, and .aif/config.yml — for human review, instead of leaving a wall of blank templates. Use once per…
Multi-agent code review covering correctness, quality, architecture, test coverage, and security
Discovers and routes to the right ai-factory skill, subagent, or MCP tool for the current task. Loaded automatically by the SessionStart hook in every repo where AIF is installed. Use when starting work, when unsure which tool to reach for, or when the work…
Skeleton for an org-specific skill — copy into skills/, rename, and fill in. Encodes a recurring multi-step workflow your org performs (a deploy runbook, a release checklist, an onboarding scaffold).
Scaffolds a new detection/analysis module in your platform's extensible service — module code, registry registration, config wiring, telemetry signal contract, and verification at every tier. Use when adding a new detection or analysis capability to a…
Adversarial review of any artifact — a spec, architecture doc, task breakdown, diff/PR, plan, README, or plain prose claim. Assumes the artifact is wrong, broken, or incomplete, tries to prove it, and reports only the findings that survive its own refutation…
Codebase health audit — identify technical debt, quality issues, and improvement opportunities
Design architecture and break requirement into tasks
End-to-end bug fix workflow — report, analyze, fix, verify, ship (PR + merge + deploy + knowledge capture)
Canary deployment with smoke tests — deploy to a zero-traffic revision, run health checks, and promote on success. Use when the user says "canary deploy", "deploy with canary", "smoke test the deploy", or wants deployment confidence before going live.
Systematic root-cause debugging for local repros, failing tests, and broken builds. Phase 1 = build a fast deterministic feedback loop (this is the skill); the rest is mechanical. Use when tests fail, builds break, or local behavior doesn't match…
Safe dependency update loop — inventory outdated/vulnerable dependencies across the repo's toolchains, vet each candidate's changelog for breaking risk, update in an isolated branch, prove it with tests (and the org regression smoke when configured), and open…
Removes an old API, field, capability, or service across every repo declared in `.aif/config.yml` `repos:` in safe stages — announce → stop new uses → migrate existing → delete. Use when ripping out a legacy endpoint, removing a column, retiring a capability,…
Find and fix documentation made stale by a code change — derive the changed public surfaces (APIs, CLI flags, config keys, env vars, endpoints) from a diff, hunt every doc that mentions them, classify stale vs missing coverage, and apply the doc updates. Use…
At the start of any non-trivial feature, identify (1) whether it introduces or changes a platform capability/invariant that needs an entry in your org's spec registry (`org.spec_registry`) FIRST, and (2) where its tests belong (org regression suite vs…
Single entry point that takes a GitHub issue and drives it through to a merge-ready PR — classifies the issue, routes to /debug or /feature-prep (and /grill-feature when criteria fire), implements in vertical slices, adds tests in the right tier, runs /ship,…
Git conventions — commit-subject prefixes that pass your CI's commit check (configured via `org.commit_prefix_regex`, defaulting to Conventional Commits), atomic commits, branch naming, when to worktree vs branch, and how to drive a PR through CI. Use when…
Adversarial design review for architectural / cross-service / contract-touching work. Interviews the user one question at a time, anchored in whatever design sources exist (`.aif/context/architecture.md`, ADRs under `org.adr_dir`, the spec registry at…
Compact the current session into a handoff document so a fresh agent (or you, after `/clear`) can pick up the work without losing context. Captures per-repo branch state across every repo touched (per `.aif/config.yml` `repos:`), in-flight PRs, MCP queries…
Builds multi-file changes in thin vertical slices, one repo at a time, with a working state at every step. Use when implementing any feature that touches more than one file, crosses repo boundaries, or feels too big to land in one commit. Particularly…
License and SBOM compliance audit — build a software bill of materials from the repo's actual dependency graph, resolve every component's license, judge each against the org's license policy (org.license_policy), and report allowed / denied / needs-review…
Remote-derived view of all in-flight AIF work — open PRs and pushed feat/REQ-* branches across every session — with a coarse component/domain overlap report. Read-only and advisory.
Scaffolds a new CRUD module following your codebase's documented module pattern (schema → migration → repository → service → handler → module registration), wires it into the server, and publishes its interface to the shared resolver layer if other modules…
API cost & performance scanner — identify expensive operations and optimization opportunities
End-to-end AIF pipeline that takes a requirement from spec through to deployed. Takes a REQ number as argument and runs validate → fix → architect → fix → implement → verify (reflect + review) → create PR → wrapup (merge, deploy, knowledge capture). Use when…
Post-implementation self-review — catch issues before /review
Draft multi-audience release notes (customer, engineering, executive) from a git tag or range — classifies commits and merged PRs by type, pulls context from linked specs, and produces a reviewable draft. Never publishes anything itself. Use when cutting a…
Proactive secret rotation with an expiry gate — walk the org's secret inventory (secrets: in .aif/config.yml), find what's expiring or over max age, and drive each rotation through the overlap pattern (issue new → deploy alongside → verify → flip → revoke…
Pre-merge orchestrator. Fans out specialist subagents in parallel against the staged change (cross-repo-impact, security-reviewer, migration-analyzer if SQL changed, cedar-policy-reviewer if your org uses Cedar and policies changed, gemini-reviewer if a…
Replaces speculation with reading the source. Before writing code that depends on a contract, schema, deployed state, or platform invariant, query the authoritative source — MCP tools when configured, your org's spec registry and ADRs when they exist,…
Write requirement specs from feature requests
Parallel pipeline orchestrator — launch multiple /proceed sessions concurrently across REQs, monitor progress, and report status. Use when the user says "sprint", "run these REQs in parallel", "proceed with all approved REQs", "launch a sprint", or wants to…
Show current state of all AIF work across the project
Detect drift across ALL the sync surfaces `/init` vendors into a project — `.aif/templates/*.md`, `.aif/partials/*.sh`, `.aif/ETHOS.md`, and the workflow runtime (`.aif/workflows/aif-sprint.workflow.js` + `README.md`) — against the canonical copies in…
Generate a STRIDE threat model from a spec, RFC, or feature description — enumerate assets, actors, trust boundaries, and data flows, walk STRIDE per element, rate what's credible, and emit a mitigations punch list as a reviewable artifact stored next to the…
Investigates a problem in your org's shared dev environment (errors, latency spike, broken endpoint, "something's wrong on dev"). Walks your observability sources in the order configured in `.aif/config.yml` — traces/dashboards → orchestrator state → data…