Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[guidelines] workshop/28-orchestrate-workflows.md: multi-line prompt violates single-sentence prompt rule

Closed Beginner friendly
  • Is something wrong?
#3,591 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
92/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Open workshop/28-orchestrate-workflows.md and locate the multi-line prompt described under the prompt-simplicity violation. Rewrite that prompt as one clear sentence while preserving the requested workflow outcome, then review the surrounding guideline examples to confirm it follows the single-sentence rule.

Written by the indexing model from the issue text.

Description

documentation guidelines

File reviewed

workshop/28-orchestrate-workflows.md

Violations

Prompt-simplicity rule (AI agent guidance)

Offending text:

/agentic-workflows create a new workflow named repo-orchestrator that reads
open PR count and checks whether a daily-status issue exists today.
If stale open PRs are found, use dispatch-workflow to trigger pr-reviewer.
If no status issue exists, use dispatch-workflow to trigger daily-status.
Add permissions: contents: read, issues: read, pull-requests: read.
Set safe-outputs: dispatch-workflow with the list of allowed workflows.

Suggested fix:
Guidelines cap every ```prompt block at "a single clear sentence" and explicitly warn against "multi-part instructions, bullet-formatted prompts, or over-engineered phrasing," leaving decomposition to the /agentic-workflows skill. This six-line prompt spells out permissions, routing conditions, and safe-outputs configuration explicitly. Replace it with one natural-language sentence describing the desired outcome, e.g. "Use the `/agentic-workflows` skill to create a `repo-orchestrator` workflow that dispatches `pr-reviewer` when stale PRs exist and `daily-status` when no status issue was created today," and let the skill work out permissions and safe-outputs.

[!WARNING]

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

  • github.github.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "github.github.com"

See Network Configuration for more information.

Generated by 📋 Guidelines Enforcer · copilot · auto · 162.9 AIC · ⌖ 14.5 AIC · ⊞ 9.1K · ◷

  • expires on Sep 27, 2026, 4:03 AM UTC
Dominant language
JavaScript
Stars
52
Forks
26
Avg merge
12h 58m
Merged PRs (30d)
15

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/gh-aw-workshop

All issues in githubnext/gh-aw-workshop

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.