---
name: ci-maintenance
description: GitHub Actions maintenance. Use when authoring or reviewing workflows or composite actions, especially event, permission, action-reference, artifact, setup, or concurrency changes.
title: ci-maintenance
canonical_url: https://skilld.dev/gh/pingdotgg/t3code/ci-maintenance
last_updated: 2026-11-12T14:20:12.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [privileged-workflows.md](https://skilld.dev/api/skills-raw/pingdotgg/t3code/ci-maintenance/privileged-workflows.md).
>
> If the user asked to install this Skill, run `npx skilld install pingdotgg/t3code/ci-maintenance`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/ci-maintenance`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/pingdotgg/t3code/ci-maintenance) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/ci-maintenance`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/ci-maintenance --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/ci-maintenance --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

Audit the trust boundary before editing. This skill owns Actions event
semantics, workflow security, permissions, action pinning, setup reuse,
untrusted inputs, timeouts, concurrency, and artifact trust boundaries.

## Workflow

1. Decide whether this is a review or an implementation. Reviews produce
   evidence-backed findings without editing; implementations continue through
   the smallest boundary-preserving change.
2. Inspect every affected workflow, composite action, and caller. List all
   affected jobs and actions before proceeding.
3. For each job, record the trigger, actor/fork status, workflow revision,
   checked-out revision, permissions, credentials, and every external input and
   consumer. Include artifacts, caches, outputs, PR fields, refs, dispatch
   inputs, generated files, and called actions.
4. Consult current GitHub documentation for every platform-sensitive decision.
   Repository examples establish local convention, not platform semantics.
5. Apply every applicable rule:
   - Default workflow permissions to empty and grant minimal job permissions.
   - Reuse the repository's shared setup action unless the environment must differ.
   - Give executable jobs intentional matrices and realistic timeouts.
   - Pin external actions and reusable workflows to full commit SHAs with
     readable release comments; verify each SHA belongs to that upstream release.
   - Analyze event choice, checkout revision, and credential persistence
     together.
   - Pass untrusted expressions through environment variables; validate and
     quote them before use.
   - Derive concurrency from interruption safety.
6. For forks, privileged credentials, publication, or cross-run data, read
   [privileged-workflows.md](https://skilld.dev/api/skills-raw/pingdotgg/t3code/ci-maintenance/privileged-workflows.md).
7. Run the narrowest syntax and repository checks, inspect the complete diff,
   and identify behavior testable only on GitHub-hosted runners.

For local patterns, inspect the current shared setup action and the nearest
workflow with the same trust boundary. Use ordinary check workflows for routine
precedent and privileged publication workflows only for equivalent trust
boundaries.

The task is complete when every affected job and caller has a recorded trust
boundary, every applicable rule has evidence or a compensating control, local
checks pass, and GitHub-only verification is identified. Reviews report every
failure with evidence; implementations resolve every failure and contain only
intended behavior.
