commit

por openai

Crie um commit git bem formado a partir das alterações atuais usando o histórico da sessão para

npx skills add https://github.com/openai/symphony --skill commit

Commit

Goals

  • Produce a commit that reflects the actual code changes and the session context.
  • Follow common git conventions (type prefix, short subject, wrapped body).
  • Include both summary and rationale in the body.

Inputs

  • Codex session history for intent and rationale.
  • git status, git diff, and git diff --staged for actual changes.
  • Repo-specific commit conventions if documented.

Steps

  1. Read session history to identify scope, intent, and rationale.
  2. Inspect the working tree and staged changes (git status, git diff, git diff --staged).
  3. Stage intended changes, including new files (git add -A) after confirming scope.
  4. Sanity-check newly added files; if anything looks random or likely ignored (build artifacts, logs, temp files), flag it to the user before committing.
  5. If staging is incomplete or includes unrelated files, fix the index or ask for confirmation.
  6. Choose a conventional type and optional scope that match the change (e.g., feat(scope): ..., fix(scope): ..., refactor(scope): ...).
  7. Write a subject line in imperative mood, <= 72 characters, no trailing period.
  8. Write a body that includes:
    • Summary of key changes (what changed).
    • Rationale and trade-offs (why it changed).
    • Tests or validation run (or explicit note if not run).
  9. Append a Co-authored-by trailer for Codex using Codex <codex@openai.com> unless the user explicitly requests a different identity.
  10. Wrap body lines at 72 characters.
  11. Create the commit message with a here-doc or temp file and use git commit -F <file> so newlines are literal (avoid -m with \n).
  12. Commit only when the message matches the staged changes: if the staged diff includes unrelated files or the message describes work that isn't staged, fix the index or revise the message before committing.

Output

  • A single commit created with git commit whose message reflects the session.

Template

Type and scope are examples only; adjust to fit the repo and changes.

<type>(<scope>): <short summary>

Summary:
- <what changed>
- <what changed>

Rationale:
- <why>
- <why>

Tests:
- <command or "not run (reason)">

Co-authored-by: Codex <codex@openai.com>

Mais skills de openai

user-context
openai
Carregar ou gerenciar as preferências de roteamento de origem duráveis, a lógica de integração, o progresso de configuração e o registro da camada semântica do plugin Data Analytics.
official
notion-research-documentation
openai
Pesquise conteúdo do Notion e sintetize em briefs estruturados, relatórios ou comparações com citações. Pesquise e busque páginas do Notion usando consultas direcionadas, depois organize os achados por tema com citações inline das fontes e uma seção de referências. Escolha entre quatro formatos de saída (brief rápido, resumo de pesquisa, comparação, relatório abrangente) com base no escopo e no objetivo do usuário. Crie e atualize páginas do Notion usando modelos integrados; vincule fontes diretamente e acompanhe alterações à medida que novas informações chegam...
official
rcsb-pdb-skill
openai
Enviar solicitações compactas do RCSB PDB para metadados principais, consultas da API de busca e downloads FASTA. Use quando um usuário desejar resumos concisos do RCSB; salve JSON bruto ou…
official
pdf
openai
We need to translate the given text from English to Brazilian Portuguese. The text describes a skill related to PDF handling. The name "pdf" is to be preserved, but it appears in the text as "PDF" (uppercase). The instruction says "Do not include the name unless it appears in the source text." Since "PDF" appears multiple times, we should keep it as is. Also preserve technical terms like "Poppler", "pdftoppm", "reportlab", "pdfplumber", "pypdf", "ASCII". The translation should be natural in Brazilian Portuguese. Let's break down the text: "PDF reading, creation, and validation with visual rendering and programmatic generation. Render PDF pages to PNG for visual inspection of layout, spacing, and typography before delivery using Poppler ( pdftoppm ) Generate PDFs programmatically with reportlab for reliable formatting; extract text and metadata with pdfplumber or pypdf Enforce quality standards: no clipped text, overlapping elements, broken tables, or rendering artifacts; ASCII hyphens only, human
official
test-coverage-improver
openai
Improve test coverage in the OpenAI Agents JS monorepo: run `pnpm test:coverage`, inspect coverage artifacts, identify low-coverage files and branches, propose…
official
playwright
openai
Automação de navegador via terminal com snapshots de elementos e fluxos de UI interativos. Opera através do script wrapper playwright-cli (requer npx); suporta modos headless e headed para depuração visual. Fluxo principal: abrir página, capturar snapshot para referências estáveis de elementos, interagir usando referências, recapturar snapshot após navegação ou mudanças no DOM. Inclui preenchimento de formulários, cliques, digitação, gerenciamento de múltiplas abas, captura de screenshot/PDF e gravação de trace para depuração de fluxos. Referências de elementos (ex.: e3, e15)...
official
ukb-topmed-phewas-skill
openai
Busque resumos compactos de PheWAS UKB-TOPMed para variantes únicas, aceitando entrada rsID, GRCh37 ou GRCh38 e resolvendo para a consulta GRCh38 necessária. Use quando um…
official
code-review-context
openai
Contexto visível do modelo
official