Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

session-summary

Étoiles17

Forks1

Mis à jour21 mai 2026 à 13:15

Create a session summary file in docs/sessions/ before merging a PR. Captures date, PR number, title, and concise summary of work done.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

MagPasulke

MagPasulke/abap-string-interpreter

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

SKILL.md

readonly

name	session-summary
description	Create a session summary file in docs/sessions/ before merging a PR. Captures date, PR number, title, and concise summary of work done.

Session Summary Skill

Create a session summary file before merging the PR. The summary must be committed to the feature branch.

File Naming Convention

docs/sessions/YYYY-MM-DD_PR-NN_short-title.md

YYYY-MM-DD — date of the session
PR-NN — PR number (e.g. PR-32). Use no-pr if no PR was created.
short-title — kebab-case summary (2-5 words)

Examples:

2026-05-21_PR-32_consolidate-duplicate-messages.md
2026-05-20_PR-19_refactor-customlogic-resolver.md
2026-05-21_no-pr_http-context-and-input-validation.md

Template

# YYYY-MM-DD PR-NN short-title

**Date:** YYYY-MM-DD
**Title:** Short descriptive title

## Summary

One paragraph. Include: what was done, key changes, artifacts created/modified, test results, PR number. Keep concise but complete enough to reconstruct context later.

Rules

Use the naming convention above — makes files sortable by date and searchable by PR
Write summary BEFORE merge (commit to feature branch)
Include PR number
Mention test results (pass/fail counts)
Reference issue numbers if applicable
Keep to one paragraph — no bullet lists, no verbose explanations

Plus depuis ce dépôt

même dépôt

adt-checkerrors

MagPasulke/abap-string-interpreter

Run ATC syntax check on the SAP system to detect syntax errors after git pull.

2026-06-1117

adt-gitpull

MagPasulke/abap-string-interpreter

Trigger an abapGit repository pull on the SAP system to sync the current codebase.

2026-06-1117

adt-rununit

MagPasulke/abap-string-interpreter

Run ABAP Unit tests on the remote SAP system via ADT.

2026-05-3017

conventional-commit

MagPasulke/abap-string-interpreter

Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.

2026-05-2817

create-tests

MagPasulke/abap-string-interpreter

Detailed guidance on which test layer(s) to update and how to write tests for different kinds of changes in the ZASIS project.

2026-05-2817

exception-handling

MagPasulke/abap-string-interpreter

Reference guide for the ZASIS exception handling pattern — class hierarchy, message class, T100 integration, how to raise exceptions, and rules for adding new exceptions.

2026-05-2617

name	session-summary
description	Create a session summary file in docs/sessions/ before merging a PR. Captures date, PR number, title, and concise summary of work done.

Session Summary Skill

Create a session summary file before merging the PR. The summary must be committed to the feature branch.

File Naming Convention

docs/sessions/YYYY-MM-DD_PR-NN_short-title.md

YYYY-MM-DD — date of the session
PR-NN — PR number (e.g. PR-32). Use no-pr if no PR was created.
short-title — kebab-case summary (2-5 words)

Examples:

2026-05-21_PR-32_consolidate-duplicate-messages.md
2026-05-20_PR-19_refactor-customlogic-resolver.md
2026-05-21_no-pr_http-context-and-input-validation.md

Template

# YYYY-MM-DD PR-NN short-title

**Date:** YYYY-MM-DD
**Title:** Short descriptive title

## Summary

One paragraph. Include: what was done, key changes, artifacts created/modified, test results, PR number. Keep concise but complete enough to reconstruct context later.

Rules

Use the naming convention above — makes files sortable by date and searchable by PR
Write summary BEFORE merge (commit to feature branch)
Include PR number
Mention test results (pass/fail counts)
Reference issue numbers if applicable
Keep to one paragraph — no bullet lists, no verbose explanations