GitHub Actions for Claude Code

This skill provides expert guidance for working with the `nakamasato/claude-code-actions` repository, which contains custom GitHub Actions for automated project workflows powered by Claude Code.

What This Skill Does

Helps you understand, develop, test, and maintain GitHub Actions that use Claude Code to generate AI-powered project summaries from multiple data sources (GitHub PRs/issues, Slack messages) and output to multiple destinations (Slack, Notion).

Repository Context

The repository contains composite GitHub Actions for automated workflows:

Instructions

When working with this repository, follow these guidelines:

1. Understanding the Architecture

The project-summary action operates in three phases:

**Phase 1: Data Collection**

**Phase 2: Analysis**

**Phase 3: Output**

2. Key Files to Understand

3. Development and Testing

**Testing the action:**

**Validating action syntax:**

```bash

yamllint project-summary/action.yml

```

**Understanding data formats:**

GitHub PRs:

```bash

gh search prs --repo owner/repo --merged --merged-at 2024-01-01..2024-02-01 --json title,body,number --limit 100

```

GitHub Issues:

```bash

gh search issues --repo owner/repo --created 2024-01-01..2024-02-01 --json title,body,number,state --limit 100

```

4. Template System

Templates are in `project-summary/templates/` and define:

Users override templates via action inputs for customization.

**Available templates:**

5. Date Period Handling

The action supports flexible date specifications:

Date calculations use bash scripts with UTC timezone handling.

6. Output Format Requirements

**Slack (mrkdwn format):**

**Notion:**

7. Authentication Requirements

**Claude Code:** Requires `claude_code_oauth_token` OR `anthropic_api_key`

**GitHub:** `GITHUB_TOKEN` (same repo) OR GitHub App token (cross-org/cross-repo)

**Slack:** `slack_bot_token` and `slack_team_id` for MCP integration

**Notion:** `notion_token` with appropriate database permissions

8. Key Design Patterns

9. Releasing New Versions

Users reference the action via:

When releasing:

1. Update version in README examples if needed

2. Create and push new git tag

3. Update release notes with changelog

4. Test with workflow runs before promoting

10. Common Tasks

**Adding a new template:**

1. Create file in `project-summary/templates/`

2. Define system_prompt, output_format, language, tone

3. Update action.yml documentation

**Supporting a new data source:**

1. Add data collection step in action.yml

2. Generate JSON output matching expected format

3. Update system prompt templates to reference new data

**Adding a new output destination:**

1. Configure MCP server in action.yml

2. Add output step using MCP tool

3. Update documentation with required secrets/tokens

Constraints

Example Usage

When a user asks to add a new template or modify the action, you should:

1. Read the existing action.yml and template files

2. Understand the current structure and patterns

3. Make changes following the established conventions

4. Update documentation if adding new features

5. Suggest testing approach via workflow runs