AgentToolHub
Skill

git-workflow

git-workflow — a Claude Code skill from blogic-cz/agent-tools

Features

  • ✓Secure AI agent CLI access
  • ✓Customizable project configurations
  • ✓Structured JSON output for LLMs
  • ✓Credential guard to protect secrets
  • ✓Curated collection of 7 tools for GitHub, Kubernetes, etc.
  • ✓Visit the GitHub repo for more details

Installation Guide

Recommended: Copy the repo URL and tell your AI agent to install it. The agent will set up everything — dev dependency, config file, credential guard, skill — in the right places for your project.

>
>
text
> Install @blogic-cz/agent-tools from https://github.com/blogic-cz/agent-tools as a dev dependency, install the agent-tools skill, set up the credential guard, and configure the tools I need for this project.
>

Manual installation

bash
bun add -d @blogic-cz/agent-tools

Skill installation

Install per-tool skills for only the tools your project uses:

bash
npx skills add blogic-cz/agent-tools --path skill/gh-tool
npx skills add blogic-cz/agent-tools --path skill/db-tool
npx skills add blogic-cz/agent-tools --path skill/k8s-tool
npx skills add blogic-cz/agent-tools --path skill/az-tool
npx skills add blogic-cz/agent-tools --path skill/logs-tool
npx skills add blogic-cz/agent-tools --path skill/session-tool

Or install the all-in-one skill that covers every tool:

bash
npx skills add blogic-cz/agent-tools --path skill/agent-tools

Requirements: Bun >=1.0.0

For agents reading this

Follow these steps to set up agent-tools in the consumer project.

Step 1 — Install

  • JavaScript/TypeScript project (has package.json): Install as a dev dependency:

    • bash
      bun add -d @blogic-cz/agent-tools

  • Non-JavaScript project (no package.json): Skip installation — run tools directly with bunx:

    • bash
      bunx gh-tool pr status
  bunx k8s-tool pods --env test

    Step 2 — Configure

    Ask the user which tools they need (gh, db, k8s, az, logs, session, audit). Create agent-tools.json5 in the project root with only the selected tools configured. See [examples/agent-tools.json5](./examples/agent-tools.json5) for the full config reference with all options documented.

    Minimal starting config:

    json5
    {
  $schema: "https://raw.githubusercontent.com/blogic-cz/agent-tools/main/schemas/agent-tools.schema.json",
}

    Step 3 — Credential Guard

    Set up the credential guard for the agent's platform:

  • Claude Code: Add the PreToolUse hook to .claude/settings.json — see [Setup for Claude Code](#setup-for-claude-code)

  • OpenCode: Create the plugin at .opencode/plugins/credential-guard.ts — see [Setup for OpenCode](#setup-for-opencode)

    • Step 4 — Test & Demo

    For each tool the user selected in Step 2:

  • Run bun <tool-name> --help to verify it works (e.g. bun gh-tool --help)

  • Summarize the key commands available

  • Show the user what data they have access to based on their agent-tools.json5 — e.g. which environments, clusters, namespaces, databases, or profiles are configured and reachable

    • Step 5 — Skill & Agent Docs

    Install only the per-tool skills the project needs (recommended), or the all-in-one skill:

    bash
    # Per-tool skills (recommended) — install only what the project uses
npx skills add blogic-cz/agent-tools --path skill/gh-tool
npx skills add blogic-cz/agent-tools --path skill/db-tool
npx skills add blogic-cz/agent-tools --path skill/k8s-tool
npx skills add blogic-cz/agent-tools --path skill/az-tool
npx skills add blogic-cz/agent-tools --path skill/logs-tool
npx skills add blogic-cz/agent-tools --path skill/session-tool

# All-in-one skill (alternative) — all tools in a single skill
npx skills add blogic-cz/agent-tools --path skill/agent-tools

    Do not run these commands for the user — they require interactive selection.

    Available per-tool skills:

    | Skill | Install when project uses |
    | -------------- | ------------------------------------------ |
    | gh-tool | GitHub PRs, issues, workflows, CI checks |
    | db-tool | SQL queries, schema introspection |
    | k8s-tool | Kubernetes pods, logs, deployments |
    | az-tool | Azure DevOps pipelines, builds |
    | logs-tool | Application log reading (local and remote) |
    | session-tool | OpenCode session history browsing |
    | agent-tools | All of the above in a single skill |

    Then update the project's AGENTS.md and/or CLAUDE.md:

  • Add rows to the skills table for each installed skill (if one exists):

    • markdown
       | GitHub PRs, issues, workflows | `gh-tool` |
   | Database queries, schema | `db-tool` |

  • Add or update the Tooling section:

    • markdown
       ## Tooling

   For tool wrappers and operational patterns, load the relevant tool skill (`gh-tool`, `db-tool`, etc.).

    Step 6 — Custom Tool Scaffold

    Create an agent-tools/ directory in the project root with an example tool so the user has a working template for building project-specific tools. Copy the scaffold from [examples/custom-tool/](./examples/custom-tool/):

    text
    agent-tools/
  package.json          # private package depending on @blogic-cz/agent-tools
  tsconfig.json         # extends root tsconfig
  noop.ts               # placeholder export for typecheck
  example-tool/
    index.ts             # ping-pong example using Effect CLI

    After creating the files, run bun install in the agent-tools/ directory (or from the workspace root if it's a monorepo). Then verify:

    bash
    bun run agent-tools/example-tool/index.ts ping

    Reviews