Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

app-store-changelog

Estrelas3

Forks0

Atualizado7 de maio de 2026 às 01:43

Generate user-facing App Store release notes from git history since the last tag.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

Ignvvcio254

Ignvvcio254/Jarvis-254-Agent

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	app-store-changelog
description	Generate user-facing App Store release notes from git history since the last tag.
risk	safe
source	Dimillian/Skills (MIT)
date_added	2026-03-25

App Store Changelog

Overview

Generate a comprehensive, user-facing changelog from git history since the last tag, then translate commits into clear App Store release notes.

When to Use

When the user asks for App Store "What's New" text or release notes from git history.
When you need to turn raw commits into concise, user-facing release bullets.

Workflow

1) Collect changes

Run scripts/collect_release_changes.sh from the repo root to gather commits and touched files.
If needed, pass a specific tag or ref: scripts/collect_release_changes.sh v1.2.3 HEAD.
If no tags exist, the script falls back to full history.

2) Triage for user impact

Scan commits and files to identify user-visible changes.
Group changes by theme (New, Improved, Fixed) and deduplicate overlaps.
Drop internal-only work (build scripts, refactors, dependency bumps, CI).

3) Draft App Store notes

Write short, benefit-focused bullets for each user-facing change.
Use clear verbs and plain language; avoid internal jargon.
Prefer 5 to 10 bullets unless the user requests a different length.

4) Validate

Ensure every bullet maps back to a real change in the range.
Check for duplicates and overly technical wording.
Ask for clarification if any change is ambiguous or possibly internal-only.

Commit-to-Bullet Examples

The following shows how raw commits are translated into App Store bullets:

Raw commit message	App Store bullet
`fix(auth): resolve token refresh race condition on iOS 17`	• Fixed a login issue that could leave some users unexpectedly signed out.
`feat(search): add voice input to search bar`	• Search your library hands-free with the new voice input option.
`perf(timeline): lazy-load images to reduce scroll jank`	• Scrolling through your timeline is now smoother and faster.

Internal-only commits that are dropped (no user impact):

chore: upgrade fastlane to 2.219
refactor(network): extract URLSession wrapper into module
ci: add nightly build job

Example Output

What's New in Version 3.4

• Search your library hands-free with the new voice input option.
• Scrolling through your timeline is now smoother and faster.
• Fixed a login issue that could leave some users unexpectedly signed out.
• Added dark-mode support to the settings screen.
• Improved load times when opening large photo albums.

Output Format

Title (optional): "What's New" or product name + version.
Bullet list only; one sentence per bullet.
Stick to storefront limits if the user provides one.

Resources

scripts/collect_release_changes.sh: Collect commits and touched files since last tag.
references/release-notes-guidelines.md: Language, filtering, and QA rules for App Store notes.

Mais deste repositório

mesmo repositório

007

Ignvvcio254/Jarvis-254-Agent

Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.

2026-05-073

accessibility-compliance-accessibility-audit

Ignvvcio254/Jarvis-254-Agent

You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.

2026-05-073

active-directory-attacks

Ignvvcio254/Jarvis-254-Agent

Provide comprehensive techniques for attacking Microsoft Active Directory environments. Covers reconnaissance, credential harvesting, Kerberos attacks, lateral movement, privilege escalation, and domain dominance for red team operations and penetration testing.

2026-05-073

ad-creative

Ignvvcio254/Jarvis-254-Agent

Create, iterate, and scale paid ad creative for Google Ads, Meta, LinkedIn, TikTok, and similar platforms. Use when generating headlines, descriptions, primary text, or large sets of ad variations for testing and performance optimization.

2026-05-073

advogado-especialista

Ignvvcio254/Jarvis-254-Agent

Advogado especialista em todas as areas do Direito brasileiro: familia, criminal, trabalhista, tributario, consumidor, imobiliario, empresarial, civil e constitucional.

2026-05-073

agent-orchestrator

Ignvvcio254/Jarvis-254-Agent

Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.

2026-05-073

name	app-store-changelog
description	Generate user-facing App Store release notes from git history since the last tag.
risk	safe
source	Dimillian/Skills (MIT)
date_added	2026-03-25

App Store Changelog

Overview

Generate a comprehensive, user-facing changelog from git history since the last tag, then translate commits into clear App Store release notes.

When to Use

When the user asks for App Store "What's New" text or release notes from git history.
When you need to turn raw commits into concise, user-facing release bullets.

Workflow

1) Collect changes

Run scripts/collect_release_changes.sh from the repo root to gather commits and touched files.
If needed, pass a specific tag or ref: scripts/collect_release_changes.sh v1.2.3 HEAD.
If no tags exist, the script falls back to full history.

2) Triage for user impact

Scan commits and files to identify user-visible changes.
Group changes by theme (New, Improved, Fixed) and deduplicate overlaps.
Drop internal-only work (build scripts, refactors, dependency bumps, CI).

3) Draft App Store notes

Write short, benefit-focused bullets for each user-facing change.
Use clear verbs and plain language; avoid internal jargon.
Prefer 5 to 10 bullets unless the user requests a different length.

4) Validate

Ensure every bullet maps back to a real change in the range.
Check for duplicates and overly technical wording.
Ask for clarification if any change is ambiguous or possibly internal-only.

Commit-to-Bullet Examples

The following shows how raw commits are translated into App Store bullets:

Raw commit message	App Store bullet
`fix(auth): resolve token refresh race condition on iOS 17`	• Fixed a login issue that could leave some users unexpectedly signed out.
`feat(search): add voice input to search bar`	• Search your library hands-free with the new voice input option.
`perf(timeline): lazy-load images to reduce scroll jank`	• Scrolling through your timeline is now smoother and faster.

Internal-only commits that are dropped (no user impact):

chore: upgrade fastlane to 2.219
refactor(network): extract URLSession wrapper into module
ci: add nightly build job

Example Output

What's New in Version 3.4

• Search your library hands-free with the new voice input option.
• Scrolling through your timeline is now smoother and faster.
• Fixed a login issue that could leave some users unexpectedly signed out.
• Added dark-mode support to the settings screen.
• Improved load times when opening large photo albums.

Output Format

Title (optional): "What's New" or product name + version.
Bullet list only; one sentence per bullet.
Stick to storefront limits if the user provides one.

Resources

scripts/collect_release_changes.sh: Collect commits and touched files since last tag.
references/release-notes-guidelines.md: Language, filtering, and QA rules for App Store notes.