agentleFS
fpindejfpindej/netrock/.claude/skills/add-ci-area/SKILL.md

add-ci-area

Skill234 starsChanged 3 months agoMITView on GitHub

Add a new project area to CI workflows

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add a path filter in the changes job:

    line 11
  2. Very specific:

    Add an output to the changes job:

    line 16
  3. Distinctive:

    Add a new job (copy an existing one and adapt):

    line 20
  4. Very specific:

    Add the new job to the gate job's needs:

    line 35
  5. Distinctive:

    Verify: push a branch and confirm the new job appears in the PR checks

    line 41
  6. Very specific:

    No branch protection changes needed - the CI passed gate job covers all upstream jobs automatically.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Adds a new project area to CI.

Steps

  1. Open .github/workflows/ci.yml
  2. Add a path filter in the changes job:
    mobile:
      - 'src/mobile/**'
  3. Add an output to the changes job:
    mobile: ${{ steps.filter.outputs.mobile }}
  4. Add a new job (copy an existing one and adapt):
    mobile-checks:
      name: Mobile checks
      needs: changes
      if: needs.changes.outputs.mobile == 'true'
      runs-on: ubuntu-latest
      timeout-minutes: 10
      defaults:
        run:
          working-directory: src/mobile
      steps:
        - uses: actions/checkout@v6
        # ... setup + build + lint + test steps
  5. Add the new job to the gate job's needs:
    ci-passed:
      needs: [backend-build, frontend-checks, mobile-checks]
  6. (If the project has a Dockerfile) Add a corresponding job to .github/workflows/docker.yml and update its on.paths and dorny/paths-filter filters
  7. Verify: push a branch and confirm the new job appears in the PR checks

No branch protection changes needed - the CI passed gate job covers all upstream jobs automatically.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.