Documentation Index

Fetch the complete documentation index at: https://docs.gofastskill.com/llms.txt

Use this file to discover all available pages before exploring further.

​

CI/CD Pipeline Integration

​

What you can automate

• Automatic Change Detection: Detect which skills have changed using git diff or file hashing
• Version Bumping: Automatically increment semantic versions (major, minor, patch)
• Artifact Creation: Package skills into ZIP files with metadata and checksums
• Blob Storage Publishing: Upload artifacts to S3 (supports S3-compatible services)
• Registry Index Management: Maintain a crates.io-like registry for skill distribution

​

Change Detection Strategies

​

Git-based Detection

fastskill package --git-diff HEAD~1 HEAD --auto-bump --output ./artifacts

• Fast and efficient
• Works well in CI/CD environments
• Can compare any two git references (commits, tags, branches)

• GitHub Actions workflows
• GitLab CI pipelines
• Any git-based CI/CD system

​

Hash-based Detection

fastskill package --detect-changes --auto-bump --output ./artifacts

• Works without git repository
• Detects any file changes
• Maintains build cache for efficiency

• Sandboxes without full git history
• Incremental packaging on a workstation

​

Version Bumping Strategies

​

Explicit Bump Type

# Major version (breaking changes)
fastskill package --detect-changes --bump major

# Minor version (new features)
fastskill package --detect-changes --bump minor

# Patch version (bug fixes)
fastskill package --detect-changes --bump patch

​

Auto-detect Bump Type

fastskill package --detect-changes --auto-bump

​

Complete Workflow Examples

​

Local packaging loop

fastskill package --detect-changes --auto-bump --output ./artifacts
fastskill publish --registry official   # or --api-url / --local-dir; see publish docs

​

Example: hosted runner (outline)

1. Check out your repository with enough history for fastskill package --git-diff <from> <to>.
2. Install the fastskill binary using the same method you use on laptops (release archive, package feed, or internal installer). Avoid hard-coding monorepo paths from the FastSkill source tree.
3. Restore secrets for registries (FASTSKILL_API_URL, tokens, cloud credentials) as environment variables.
4. Run fastskill package … then fastskill publish … with the flags from package and publish.

# Illustrative fragment only — adjust names, triggers, and secrets to your org
jobs:
  skills:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 2
      - name: Install FastSkill CLI
        run: |
          # Use your standard install path (release tarball, package, or internal mirror)
          fastskill -V
      - name: Package changed skills
        run: fastskill package --git-diff HEAD~1 HEAD --auto-bump --output ./artifacts
      - name: Publish
        run: fastskill publish --local-dir ./upload
        env:
          FASTSKILL_API_URL: ${{ secrets.FASTSKILL_API_URL }}

​

Other runners

// Jenkins-style pseudocode — replace install and credentials with yours
pipeline {
    agent any
    
    environment {
        AWS_ACCESS_KEY_ID = credentials('aws-access-key-id')
        AWS_SECRET_ACCESS_KEY = credentials('aws-secret-access-key')
    }
    
    stages {
        stage('Package') {
            steps {
                sh '''
                    fastskill package \
                        --git-diff HEAD~1 HEAD \
                        --auto-bump \
                        --output ./artifacts
                '''
            }
        }
        
        stage('Publish') {
            steps {
                sh '''
                    fastskill publish \
                        --artifacts ./artifacts \
                        --api-url "${FASTSKILL_API_URL}"
                '''
            }
        }
    }
}

​

Configuration Best Practices

​

Environment Variables

# AWS S3
export AWS_ACCESS_KEY_ID=your-key
export AWS_SECRET_ACCESS_KEY=your-secret

# Blob storage base URL
export BLOB_BASE_URL=https://blob.example.com/skills

​

Configuration Files

[blob_storage]
type = "s3"
bucket = "skills-registry"
region = "us-east-1"
# Credentials from environment variables

[registry]
git_url = "https://github.com/GoFastSkill/skill-registry.git"
branch = "main"
blob_base_url = "https://blob.example.com/skills"

​

Build Cache

​

Troubleshooting

​

No Skills Detected

1. Check that skills directory exists and contains SKILL.md files
2. Verify git diff is working: git diff HEAD~1 HEAD --name-only
3. Check build cache for stale entries
4. Use --force to package all skills regardless of changes

​

Version Bumping Issues

1. Ensure skill-project.toml exists or can be created
2. Check that version format is valid semver (e.g., “1.2.3”)
3. Verify write permissions for skill-project.toml

​

Blob Storage Upload Failures

1. Verify credentials are correct
2. Check network connectivity to storage endpoint
3. Ensure bucket/container exists and is accessible
4. Verify IAM permissions for S3 buckets

​

Registry Index Issues

1. Ensure git repository is accessible
2. Check git credentials and permissions
3. Verify registry path exists and is writable
4. Ensure blob base URL is correct

​

See Also

• Package Command
• Publish Command
• Blob Storage Guide