OpenParable
Skip to content
← Back to skills

Github Workflow

Productivity
github-workflow

Github Workflow is an Agent Skill for productivity published in the Tracer-Cloud/opensre repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use GitHub workflow tools to read work status, draft reports, summarize follow-ups, and execute only approved issue mutations.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Tracer-Cloud/opensre/blob/HEAD/integrations/github/tools/workflow/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/github-workflow, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

GitHub Workflow

Use this workflow when the user asks about GitHub engineering status, PR readiness, community follow-ups, or turning an explicit Slack request into a GitHub issue.

  1. Read before reporting. Use the read-only GitHub tools first, and treat missing or failed reads as incomplete status rather than proof that there are no blockers.
  2. Report or summarize from known data. Use generate_work_status_report for Slack-ready status and summarize_community_followups for unanswered contributor questions or agenda items.
  3. Propose mutations before execution. Use propose_github_issue_mutation_from_slack only for explicit Slack-sourced create, update, or close requests.
  4. Execute only through approval. execute_github_issue_mutation is the only mutating GitHub workflow tool. It is never an investigation action and must remain chat-only, approval-gated, and proposal-driven.