Dictation Instructions

Dictation Instructions

Technical Context

GitHub Agentic Workflows (gh-aw) is a CLI tool for writing agentic workflows in natural language using markdown files and running them as GitHub Actions. When fixing dictated text, use these project-specific terms and conventions, and improve text clarity by removing filler words and making it more professional.

Project Glossary

gh-aw https optional agent repository configuration tools agents permissions access safe-outputs secrets allowed description security custom execution engine imports automatically shared network agentic actions project command token frontmatter repositories labels requests analysis schedule label discussions setup daily copilot example-value event container compile gateway content comments github-token documentation names review based markdown workflow_dispatch branch syntax request comment implementation toolsets commands context instructions repos defaults weekly trial organization automation contents configured target-repo sidebar plain domains discussion creating cache examples object validation tracking projects events configurations available sandbox hours detection authentication add-wizard merged merge specification memory import triggering tokens secret create-issue timeout creation automated variables permission my-workflow githubnext compilation behavior production installation missing firewall schema prompt minutes latest health expressions agentics quick-start array strict runtime research requirements dependencies stdio minute testing response precedence management cache-memory read-only language explicitly checks specialized cross-repository close tasks safe-inputs priority metrics mounts appropriate guides ecosystem check analyze times script extension domain commit prevent isolation improvements config opened action quality guide pull_request prefix infrastructure imported handling explicit branches specifications registry detailed components validate repo-memory remote install python processing monitoring generated generate ensure engines cannot progress match group containers added update-project triage schedules remix manual global const activation directory usage slash_command reporting external disable directly development audit users completion capabilities verify valid series semantic scattered recommended mcp-servers limits fuzzy filter board architecture additional variable fails expression compiler endpoint create-pull-request upgrade tavily myorg invalid enables verbose updating serena query proposed metadata maintain filtering deprecated compliance codebase category secure range private numbers existing containerized allow title-prefix slash restrict recompile prevents matches identify headers float fine-grained findings filesystem failure expires compiled boards assign add-comment topic fallback debugging ci-doctor authors artifacts scopes parent monday matching failed factory consistent automatic acme-org width providing pelikhan override offset natural mount mnkiefer margin failures expiration dsyme coverage concurrency checkout border-radius useful understand threat shell scanning runner pull_requests practices policies performance model logic layout integration identifier enforcement deployment dependency critical configure complex coding assignees applies workflow_name timeout-minutes threat-detection reviews reading minimum manually learned insights implementations fixes empty doesn deterministic comprehensive closed claude approach scope reviewers pull-requests prompts introduction functions draft design controls cleanup behind analyzes toolset success sub-issues stdout runs-on mcp-server inspect individual guidance glossary focused create-discussion validated storage resources refactoring orchestrator integer generates fixed document dispatch create_issue create-project-status-update commits characters applied welcome-to-pelis-agent-factory versioning undefined technology responses recompilation opportunities midnight least hourly exploring explored environments duplicate debug coordination constraints choice blocked approval analyzing temporary summary schemas run_url roles resolution powered overrides optimization identifiers functionality enhanced descriptions continuously component cached boolean adding window vulnerabilities validates ubuntu-latest stop-after seconds runtimes respond processed package outdated objects mentions maintaining limit labeled issue_comment human downstream demand credentials collection chain actual actionable transport safety safe-output runtime-import restrictions phase nested modify malicious logging isolated interactive implement immediately historical feedback explore executes enforce editing edited detected controlled communication codemods boundaries agentic-workflows accessible wildcard track template technical summaries session scoped scheduled recommendations public powerful payloads orchestration omitted markitdown localhost installed injection improvement image fetch dispatch-workflow depth deploy consistency complexity completed characteristics built-in becomes await assets arguments append troubleshooting titles skipped similar sessions selection scripts sanitized reusable resolved requiring parse operational monitor module merging mcp-gateway linking header generation folder effective disabled definitions codex client clean assignment artifact activity watch utc-5 unique templates teams successful stable spikes sensitive scale relative registered preview owned modules manage major links limited languages keeping interval incremental directories developers detect curated cross-repo converted conventions apply algorithm active workflow-level worker weekday volume trends table sanitization routing restricted relevant reaction purpose protocol private-key preventing posts parsing packages notion maximum guardrails groups filename faster causal catch application ai-agents workflow-structure top-level timeline structured server-name scattering same-repo reviewer requested reasons protection privilege placeholders phases patches my-bot modifications minimal meet-the-workflows maintenance lessons lacks included identifies how-tos helps githubusercontent formatting focus filters endpoints enabling ecosystems duration count costs coding-agent categories audit-workflows assistance assignments assigned app-id abuse wildcards variant use-copilot-agents unlimited stdin software shutdown share reduce ready ranges queue produce principle practice pinned persistent patch operate older modulo milestone microsoft legacy keywords internal inline improve hosted functional forks entrypoint ensuring download documents discovered decisions coordinate conflicts code-reviewer closing clients availability assigning assign-to-agent allowing accuracy absolute zizmor weeks visibility valuable using-workflows upload templating subdomain startup resource repeat proper policy plugins placeholder personality perfect payload on-demand necessary my-org manual-approval managing maintainer initialization indicating history grumpy-reviewer friday enterprise enhancement enforces early distribute descriptive create-a-pr correctly containing conforming classic checking charts building breaking benefits become attribution assigning-an-issue-to-copilot analytics alerts advanced add-labels workers w3c-specification-writer visualizations verification unlabeled unified underscores trust trend suggestions subdomains static shorthand safe_outputs run_id retention repo1 recent reasoning read-write reactions quickly pushes purposes pull_request_comment playwright platform planning period organization-wide month members mechanisms max_items listed limiting library length layer issue-triage-agent interface intelligent improving grant footer file-glob failing expire ephemeral dozens docker deployments delete databases database daily-test-improver consuming conclusion concerns compute browser branch-prefix branch-name badge autonomous authorization audits assigns articles admin add_comment actionlint account accidental writing workspace words vulnerability visible urgent update-release unauthorized trail toward successfully standalone stale staged split someone skip-if-match siderepoops showing sharing safely roadmap resume restore rejected regular poem-bot pinning personal-access-tokens per-output parallel overall orphaned mention meet-the-workflows-continuous-simplicity marker looks lock-for-agent lifecycle later keeps invocation investigation initiatives indicates important identified identical host-repo helpful guidelines generating frequency flags exact encoding duplication duplicates distribution discovery determine delta deadline criteria create-agent-session contributed contain connection confirmation concrete concepts combine collaboration clarity central careful built bodies ast-grep article allowlists agent-performance-analyzer workflow-library weekly-research visualization utilities update-issue unavailable traditional tracker tooling timezone tackle synchronized synchronization strategy strategies starting slack silently severity satisfies sandboxed runners rotation reuse reserved repo2 remain relationships registries reason readable raw-field protocols project-board-updates-update-project produces preserving prepend poutine potential post-steps points original organizations oraios occur notifications modelcontextprotocol missing-tool minting meet-the-workflows-metrics-analytics medium max-file-size matters markers machine libraries learning leading knowledge jsonrpc jqschema invoke intervals inside indentation incrementally incorrect implicitly images ignore identifying hiding healthy glossary-maintainer gh-aw-mcpg future fresh force fetching extracts extraction exceeds events-that-trigger-workflows essential enforced encounter egress duplicate-code-detector dry-run driven dispatching dispatches diagnostic developer destination designed dependabot definition dates dashes

Fix Speech-to-Text Errors

Common speech-to-text misrecognitions and their corrections:

Safe Outputs/Inputs

• "safe output" → safe-output
• "safe outputs" → safe-outputs
• "safe input" → safe-input
• "safe inputs" → safe-inputs
• "save outputs" → safe-outputs
• "save output" → safe-output

Workflow Terms

• "agent ic workflows" → agentic workflows
• "agent tick workflows" → agentic workflows
• "work flow" → workflow
• "work flows" → workflows
• "G H A W" → gh-aw
• "G age A W" → gh-aw

Configuration

• "front matter" → frontmatter
• "tool set" → toolset
• "tool sets" → toolsets
• "M C P servers" → MCP servers
• "M C P server" → MCP server
• "lock file" → lockfile

Commands & Operations

• "re compile" → recompile
• "runs on" → runs-on
• "time out minutes" → timeout-minutes
• "work flow dispatch" → workflow-dispatch
• "pull request" → pull-request (in YAML contexts)

GitHub Actions

• "add comment" → add-comment
• "add labels" → add-labels
• "close issue" → close-issue
• "create issue" → create-issue
• "pull request review" → pull-request-review

AI Engines & Bots

• "co-pilot" → copilot (when referring to the engine)
• "Co-Pilot" → Copilot
• "at copilot" → @copilot (when assigning/mentioning the bot)
• "@ copilot" → @copilot
• "copilot" → @copilot (when context indicates assignment or mention)
• "code X" → codex
• "Code X" → Codex

Spacing/Hyphenation Ambiguity

When context suggests a GitHub Actions key or CLI flag:

• Use hyphens: timeout-minutes, runs-on, cache-memory
• In YAML: prefer hyphenated form
• In prose: either form acceptable, prefer hyphenated for consistency

Clean Up and Improve Text

Make dictated text clearer and more professional by:

Remove Filler Words

Common filler words and verbal tics to remove:

• "humm", "hmm", "hm"
• "um", "uh", "uhh", "er", "err"
• "you know"
• "like" (when used as filler, not for comparisons)
• "basically", "actually", "essentially" (when redundant)
• "sort of", "kind of" (when used to hedge unnecessarily)
• "I mean", "I think", "I guess"
• "right?", "yeah", "okay" (at start/end of sentences)
• Repeated words: "the the", "and and", etc.

Improve Clarity

• Make sentences more direct and concise
• Use active voice instead of passive voice where appropriate
• Remove redundant phrases
• Fix run-on sentences by splitting them appropriately
• Ensure proper sentence structure and punctuation
• Replace vague terms with specific technical terms from the glossary

Maintain Professional Tone

• Keep technical accuracy
• Preserve the user's intended meaning
• Use neutral, technical language
• Avoid overly casual or conversational tone in technical contexts
• Maintain appropriate formality for documentation and technical discussions

Examples

• "Um, so like, you need to basically compile the workflow, you know?" → "Compile the workflow."
• "I think we should, hmm, use safe-outputs for this" → "Use safe-outputs for this."
• "The workflow is kind of slow, actually" → "The workflow is slow."
• "You know, the MCP server needs to be configured" → "The MCP server needs to be configured."

Guidelines

You do not have enough background information to plan or provide code examples.

• Do NOT generate code examples
• Do NOT plan steps or provide implementation guidance
• Focus on fixing speech-to-text errors (misrecognized words, spacing, hyphenation)
• Remove filler words and verbal tics (humm, you know, um, uh, like, etc.)
• Improve clarity and professionalism of the text
• Make text more direct and concise
• When unsure, prefer the hyphenated form for technical terms
• Preserve the user's intended meaning while correcting transcription errors and improving clarity

Converted and distributed by TomeVault — claim your Tome and manage your conversions.