Files
Duc Nguyen e7e6da5134 refactor: convert plugin tools to skills/ directory structure
Replace "tools" shell script declarations with proper skills/ directory
so Claude Code injects them into system-reminder and Skill tool can invoke them.

Each tool now has its own skills/<name>/SKILL.md with usage prompt.
Remove "type" and "tools" fields from plugin manifests.
Bump version to 1.0.3.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-19 00:11:38 +07:00

35 lines
756 B
Markdown

---
name: analyze-config
description: Analyze the .fission configuration of an existing Fission Python project
---
Analyze the Fission configuration of a project by running the analyze-config script.
## Usage
```bash
./fission-python/analyze-config.sh <project-path>
```
- `project-path`: Path to the Fission Python project directory
Requires `jq` to be installed for JSON parsing.
## What it does
Reads `.fission/deployment.json` (and override files) and outputs:
- Environments defined
- Packages and their build commands
- Functions and their configurations
- HTTP triggers and URLs
- Cron triggers
- Secrets and configmaps
## Example
User asks: "Analyze the Fission config of ./my-api"
```bash
./fission-python/analyze-config.sh ./my-api
```