Write JavaScript for actions/github-script@v8 in GitHub Actions. Apply consistent logging, pass outputs and environment variables to later steps, publish readable summaries, and handle errors with the action's provided utilities.
Write robust JavaScript for GitHub Actions github-script steps.
Review the instructions the agent will receive before you install.
Use these guidelines for JavaScript executed by actions/github-script@v8.
@actions/core and @actions/github packages globally@actions/corecore.info, core.warning, core.error for logging, not console.log or console.errorcore.setOutput to set action outputscore.exportVariable to set environment variables for subsequent stepscore.getInput to get action inputs, with required: true for mandatory inputscore.setFailed to mark the action as failed with an error messageUse core.summary.* function to write output the step summary file.
core.summary.addRaw() to add raw Markdown content (GitHub Flavored Markdown supported)core.summary.write() to flush pending writescore.summary.addRaw(...).addRaw(...).write()any type as much as possible, use specific types or unknown insteadcatch (error) {
core.setFailed(error instanceof Error ? error : String(error));
}
core.setFailed also calls core.error, so do not call bothRun make js to run the typescript compiler.
Run make lint-cjs to lint the files.
Run make fmt-cjs after editing to format the file.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.
Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.
Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.
Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.
Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.
Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.