Adoption

Agent Skills are supported by leading AI development tools.

VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory

Automattic/release

Name: release
Author: Automattic

.agents/skills/release/SKILL.md

npx skillsauth add Automattic/wordpress-atmosphere release

Clean

TrivyContainer and dependency vulnerability scanner

Clean

SemgrepStatic code analysis for vulnerabilities

Clean

mcp-scan (Snyk)Model Context Protocol security validation

Skipped

Snyk (dep)Open source security scanning

Skipped

Socket.devSupply chain security analysis

Skipped

VirusTotalMulti-engine malware detection

Skipped

CrowdStrikeAdvanced threat intelligence

Skipped

OSV-ScannerOpen Source Vulnerability database check

Skipped

OWASP Dep-Check

ATmosphere Release Process

Quick reference for managing releases and changelogs for the WordPress ATmosphere plugin.

Quick Reference

Release Commands

bin/release.sh [version]    # Build release ZIP with production deps only.
composer changelog:add      # Add a changelog entry.
composer changelog:write    # Write changelog entries to CHANGELOG.md.

Version File Locations

When updating versions manually, change these files:

atmosphere.php - Plugin header (Version: X.Y.Z) and ATMOSPHERE_VERSION constant.
readme.txt - WordPress.org readme (Stable tag: X.Y.Z).
package.json - npm version ("version": "X.Y.Z").
CHANGELOG.md - Changelog file (auto-updated by changelogger).

Changelog Management

How It Works

Changelogs are managed through the Jetpack Changelogger:

Adding entries:
```
composer changelog:add
```
- Select significance: Patch/Minor/Major.
- Select type: Added/Fixed/Changed/Deprecated/Removed/Security.
- Write message ending with punctuation!
- Saves to .github/changelog/ directory.
Writing changelog:
```
composer changelog:write
```
- Aggregates all entries from .github/changelog/.
- Updates CHANGELOG.md automatically.

Critical Requirements

Always end changelog messages with punctuation:

Good: Add support for custom post types.
Good: Fix OAuth token refresh failing silently.
Bad:  Add support for custom post types
Bad:  Fix OAuth token refresh failing silently

Write end-user friendly messages:

Focus on user benefit, not implementation details.
Avoid technical jargon where possible.
Describe what users can now do, not how it works internally.

Good: Fix posts not appearing on Bluesky when published via Quick Edit.
Good: Add option to disable standard.site document records.
Bad:  Refactor Publisher class to handle edge case in applyWrites batch.
Bad:  Fix TID collision in transformer output.

Never mention AI tools or coding assistants in changelog messages.

Version Numbering

Semantic versioning:

Major (X.0.0) - Breaking changes.
Minor (0.X.0) - New features, backward compatible.
Patch (0.0.X) - Bug fixes only.

Release Workflow

# 1. Write changelog.
composer changelog:write

# 2. Update version numbers in all version file locations.

# 3. Commit version bump.
git add -A
git commit -m "Release version X.Y.Z"

# 4. Build release ZIP.
bin/release.sh X.Y.Z

# 5. Create GitHub release with the ZIP.
gh release create X.Y.Z atmosphere-X.Y.Z.zip --title "X.Y.Z" --generate-notes

Automattic/release

.agents/skills/release/SKILL.md

Version management and release processes using Jetpack Changelogger. Use when creating releases, managing changelogs, bumping versions, or preparing releases.

20 stars

documentation

Updated Apr 16, 2026

$ install --global

skillsauth

npx skillsauth add Automattic/wordpress-atmosphere release

Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.

Security Scan Results

3 of 9 scanners reported clean

Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.

Scanners Passed

Scanners in report

Clean

TrivyContainer and dependency vulnerability scanner

95%

Clean

SemgrepStatic code analysis for vulnerabilities

95%

Clean

mcp-scan (Snyk)Model Context Protocol security validation

95%

Skipped

Snyk (dep)Open source security scanning

50%

Skipped

Socket.devSupply chain security analysis

50%

Skipped

VirusTotalMulti-engine malware detection

50%

Skipped

CrowdStrikeAdvanced threat intelligence

50%

Skipped

OSV-ScannerOpen Source Vulnerability database check

50%

Skipped

OWASP Dep-Check

50%

Last scanned: Apr 16, 2026, 10:45 PM34.3s1 file scanned

SKILL.md

name:: release
description:: Version management and release processes using Jetpack Changelogger. Use when creating releases, managing changelogs, bumping versions, or preparing releases.

ATmosphere Release Process

Quick reference for managing releases and changelogs for the WordPress ATmosphere plugin.

Quick Reference

Release Commands

bin/release.sh [version]    # Build release ZIP with production deps only.
composer changelog:add      # Add a changelog entry.
composer changelog:write    # Write changelog entries to CHANGELOG.md.

Version File Locations

When updating versions manually, change these files:

atmosphere.php - Plugin header (Version: X.Y.Z) and ATMOSPHERE_VERSION constant.
readme.txt - WordPress.org readme (Stable tag: X.Y.Z).
package.json - npm version ("version": "X.Y.Z").
CHANGELOG.md - Changelog file (auto-updated by changelogger).

Changelog Management

How It Works

Changelogs are managed through the Jetpack Changelogger:

Adding entries:
```
composer changelog:add
```
- Select significance: Patch/Minor/Major.
- Select type: Added/Fixed/Changed/Deprecated/Removed/Security.
- Write message ending with punctuation!
- Saves to .github/changelog/ directory.
Writing changelog:
```
composer changelog:write
```
- Aggregates all entries from .github/changelog/.
- Updates CHANGELOG.md automatically.

Critical Requirements

Always end changelog messages with punctuation:

Good: Add support for custom post types.
Good: Fix OAuth token refresh failing silently.
Bad:  Add support for custom post types
Bad:  Fix OAuth token refresh failing silently

Write end-user friendly messages:

Focus on user benefit, not implementation details.
Avoid technical jargon where possible.
Describe what users can now do, not how it works internally.

Good: Fix posts not appearing on Bluesky when published via Quick Edit.
Good: Add option to disable standard.site document records.
Bad:  Refactor Publisher class to handle edge case in applyWrites batch.
Bad:  Fix TID collision in transformer output.

Never mention AI tools or coding assistants in changelog messages.

Version Numbering

Semantic versioning:

Major (X.0.0) - Breaking changes.
Minor (0.X.0) - New features, backward compatible.
Patch (0.0.X) - Bug fixes only.

Release Workflow

# 1. Write changelog.
composer changelog:write

# 2. Update version numbers in all version file locations.

# 3. Commit version bump.
git add -A
git commit -m "Release version X.Y.Z"

# 4. Build release ZIP.
bin/release.sh X.Y.Z

# 5. Create GitHub release with the ZIP.
gh release create X.Y.Z atmosphere-X.Y.Z.zip --title "X.Y.Z" --generate-notes

Related Skills

Automattic/test

development

VerifiedTrustedCommunity

Testing patterns for PHPUnit tests. Use when writing tests, debugging test failures, setting up test coverage, or implementing test patterns for ATmosphere features.

20SKILL.mdUpdated Apr 16, 2026