prepare-pull-request

Stars11

Forks14

UpdatedJuly 18, 2026 at 11:26

Prepare Memory Service changes for pull request submission. Use whenever Codex is asked to create, open, submit, publish, or ready a pull request, or to perform final PR preflight. Require `task generate` before the final PR commit so generated sources and repository-wide formatting are included.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

chirino

chirino/memory-service

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	prepare-pull-request
description	Prepare Memory Service changes for pull request submission. Use whenever Codex is asked to create, open, submit, publish, or ready a pull request, or to perform final PR preflight. Require `task generate` before the final PR commit so generated sources and repository-wide formatting are included.

Prepare Pull Request

Run this workflow before invoking any commit or pull-request publishing workflow.

Inspect git status --short and preserve unrelated user changes.
From the repository root, run:
```
task generate
```
This is the canonical generation and formatting command for the repository. Do not substitute narrower formatters for this required preflight.
If task generate fails, diagnose the failure and stop PR submission until it succeeds. Do not submit a PR with partially generated output.
Review git status --short and the complete diff after generation. Keep intended generated and formatting changes in the PR; do not silently discard unexpected changes.
Run git diff --check and the verification required for the affected modules. Use the build-test skill to select those commands.
Ensure every intended change produced by task generate is committed before creating or updating the PR. If generation ran after the previous final commit, create the required follow-up commit before submission.

Report the task generate result and the verification performed when handing off the PR.

More from this repository

same repository

verify-dependabot-prs

chirino/memory-service

Batch, validate, and consolidate open Dependabot pull requests for memory-service. Use when asked to inspect the Dependabot queue, verify dependency PRs efficiently, reproduce dependency-update CI failures, combine compatible dependency PRs, or create a validated consolidated dependency PR.

2026-07-3111

operationevent-logging

chirino/memory-service

Implement or review Memory Service backend operational logging. Use for REST or gRPC boundaries, provider errors, error wrapping, background workers and task attempts, indexers and maintenance jobs, SSE or gRPC streams, request correlation, and changes under internal/operationevent.

2026-07-1911

testing

chirino/memory-service

Use when writing or debugging tests for memory-service. Covers Cucumber BDD patterns and failure reporting.

2026-07-1611

build-test

chirino/memory-service

Use when you need build, test, or dev commands for memory-service across Go, Java, frontend, or Python modules.

2026-07-1111

enhancement-docs

chirino/memory-service

Use when writing or editing enhancement documents in docs/enhancements/. Provides format, conventions, and numbering guidance.

2026-07-0911

openapi-workflow

chirino/memory-service

Use when making changes to the OpenAPI contract. Workflow for updating spec and regenerating clients.

2026-04-2911

name	prepare-pull-request
description	Prepare Memory Service changes for pull request submission. Use whenever Codex is asked to create, open, submit, publish, or ready a pull request, or to perform final PR preflight. Require `task generate` before the final PR commit so generated sources and repository-wide formatting are included.

Prepare Pull Request

Run this workflow before invoking any commit or pull-request publishing workflow.

Inspect git status --short and preserve unrelated user changes.
From the repository root, run:
```
task generate
```
This is the canonical generation and formatting command for the repository. Do not substitute narrower formatters for this required preflight.
If task generate fails, diagnose the failure and stop PR submission until it succeeds. Do not submit a PR with partially generated output.
Review git status --short and the complete diff after generation. Keep intended generated and formatting changes in the PR; do not silently discard unexpected changes.
Run git diff --check and the verification required for the affected modules. Use the build-test skill to select those commands.
Ensure every intended change produced by task generate is committed before creating or updating the PR. If generation ran after the previous final commit, create the required follow-up commit before submission.

Report the task generate result and the verification performed when handing off the PR.