Creator profile

mgiovani

Review Skills published by mgiovani, their source repositories, maintenance signals, and identity status.

Skills
7
Repository stars
6
Identity status
Source-linked

Provenance

Source and identity

Source-linked
Profile type
Creator
Canonical name
mgiovani
Public sources
1
License context
MIT

Source entries

Agent Skills from mgiovani

Repository stars and maintenance signals provide context, but do not automatically become an individual Skill's quality score.

Computed 936

mgiovani/cc-arsenal

ci-local

Run the checks a GitHub Actions workflow would run, locally, when Actions is unavailable or out of quota. Parses .github/workflows/*.yml, extracts the jobs/steps that gate merges (lint, typecheck, test, build), translates them to local commands respecting the workflow's pinned node/python versions and env, executes them sequentially, and reports a parity table of what passed locally vs. what can't be replicated (service containers, secrets, matrix dimensions) and why. Activates on "CI quota", "A

Computed 956

mgiovani/cc-arsenal

create-skill

Create a new agent skill (or Claude Code slash command) from a plain-language description, using live spec fetching, pattern research, and an approval-gated blueprint before any files are written. Use whenever the user wants to build, scaffold, or author a new skill, subagent capability, or slash command, including phrasings like 'make a command for X', 'create a slash command', 'turn this into a reusable skill', or 'package this workflow as a skill'. Not for editing CLAUDE.md/AGENTS.md memory r

Computed 946

mgiovani/cc-arsenal

implement-feature

Implements a new feature end-to-end as a senior staff engineer would, discovers project conventions, researches current best practices, drafts a plan for approval, then builds it (with parallel subagents where available) reusing existing code, skipping speculative abstractions, and verifying with tests before completion. Use when the user wants to implement, build, add, or ship new functionality (a feature, endpoint, component, module, or integration). Not for fixing an existing bug (use fix-bug

Computed 926

mgiovani/cc-arsenal

nanobanana

Generates and edits images by calling Google's Nano Banana / Gemini image generation API (requires a GEMINI_API_KEY), a real, billed API call. This skill is explicit-invocation only: use it only when the user names it or the Gemini path directly ("nanobanana", "nano banana", "gemini image generation", "GEMINI_API_KEY", "use nanobanana to …") or wants to integrate the Nano Banana / Gemini image API into their own codebase. For any implicit or general image-generation request ("generate an image",

Computed 926

mgiovani/cc-arsenal

refactor

Restructures existing code without changing its behavior: maps callers and test coverage, adds characterization tests where coverage is thin, then applies the change in small steps verified against the full test suite after each one. Use when the user wants to refactor, extract a method or class, simplify logic, reduce duplication, improve naming, restructure modules, or pay down technical debt in code that already works. Not for adding new functionality (use implement-feature) or fixing broken

Computed 916

mgiovani/cc-arsenal

team-implement

Spec-driven team orchestration for large, multi-component features or new epics: writes a full spec/design/review artifact trail under .specs/, gates code changes behind an explicit user approval, then scales a team from 3 (lite) to roughly 9 (full) agents based on complexity. Use for sizable features spanning frontend+backend+DB, unfamiliar domains, or anything you want a reviewable spec for before code is touched. Not for small/single-component changes (use implement-feature, no spec overhead)

Computed 976

mgiovani/cc-arsenal

team-review

Multi-agent review team: architecture, security, performance, testing, style, docs/UX, plus an adversary that cross-examines the other 6, for security-sensitive, architectural, or large PRs (15+ files) where a single-agent pass risks missing cross-cutting issues. Use for auth/payments/PII changes, schema/pattern changes, compliance sign-off, or when asked to 'get the review team on this' / 'multi-agent review' / 'thorough review before merge'. For a standard PR or a quick pre-merge check, use /r

Pinned paths

Every entry links to a specific source path and commit when available.

Repository context

Activity, license, and repository-level popularity are shown as context.

Open the source

Inspect the public repository