post-changes

• SKILL.mdcore · 4,157 bytes
• agents/openai.yamlasset · 158 bytes

# Post the changes to Pachca

Write a post about what changed for the chats or the thread the user named with the command, and leave it as a draft there. The changes come from the task, merge request or branch the user gave, or from this session's work if they gave none. If no target is named and none is written down for the project (step 1), ask for it. Follow the `pachca-messaging` skill for writing, drafts and editing, its «Writing to colleagues» section included.

1. Where. Find each named chat with `pachca_search_chats`, and a thread from its link as in the `pachca-search` skill. Rules for such posts may already be written down in the project's instructions for agents (`AGENTS.md`, `CLAUDE.md` or the program's own rules), or in the chat's description (`pachca_get_chat`): they come first. If a name matches several chats, show the candidates by name and ask. Several targets get one post each, written for that chat's readers.
2. What changed. Collect only what is done: the task and the merge request through the tools this session already has for them (a tracker's MCP server, `gh`, `glab`), the branch with `git log` and `git diff`, or this session's commits and changed files. Do not invent a task number, link or status you did not read, and say what you could not check. If it matters where the change is live, staging or production, and nothing says, ask.
3. How this chat writes. Read the latest page of the chat (`pachca_list_chat_messages`), above all the user's own posts of this kind, and follow their shape: the first line (for example the task number and title as a link), length, order, which links they keep and what they leave out. With no such posts, start with the task as a link and then say what changed for this chat's readers: behavior, API fields and contracts, rights, in a few short paragraphs. Name new fields and values exactly. Leave out code internals, plans and anything not done, bare URLs, the merge request link and mentions, unless the chat's posts or the user ask for them.
4. Leave a draft. Put the post into the chat's input box with `pachca_create_draft`, then show the user the text and say which chat it is in: a draft reaches nobody until they send it. A `409` means the chat already holds a draft: if it is not yours from an earlier run of this command, show it and ask before replacing it. If the user asked to see the text first, show it and create the draft after their yes. Send instead only when the user said «отправь» with the command, and only to the named targets. A bot token has no drafts: say so and show the text.
5. Run again for the same task, after the code changed or the user corrected the text. Update the draft you left (`pachca_list_drafts`, then `pachca_update_draft`). If it is gone because the user sent it, find their post among the latest messages of the chat and fix it by the editing rule of the `pachca-messaging` skill: check who has read it, then edit, or edit and reply with what changed. If the chat keeps the status of the work in a pinned message of the user's, offer to update that message instead of adding a post.

Corrections the user makes to the text are rules for this chat: when the project keeps such rules in its instructions for agents, offer to add them there, so the next post starts from them.