agentleFS
Sign inStart free
hyodotdevhyodotdev/openiap/.claude/skills/openiap-workflows/SKILL.md

openiap-workflows

Skill166 starsChanged 5 months agoMITView on GitHub

Use for OpenIAP monorepo work that should follow the repository's slash-command workflows when the user asks in natural language instead of typing a slash command, including review-pr, audit-code, audit-security, audit-iapkit, compile-knowledge, verify-all, e2e-tests, stable or prerelease package releases, resolve-issue, commit/push/PR, generated type sync, package-specific checks, GitHub review threads, and project conventions from AGENTS.md.

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. Distinctive:

    Follow both; this file only adds the Claude Code specifics.

    line 10
  2. Distinctive:

    When the user asks in natural language, execute the matching workflow by reading the command file (or invoke the slash command directly …

    line 14
  3. Very specific:

    Verify all / monorepo health check → .claude/commands/verify-all.md (/verify-all)

    line 28
  4. Very specific:

    Commit, push, or create PR → .claude/commands/commit.md (/commit)

    line 33
  5. Very specific:

    Read the "Source Of Truth", "Internal Workflow Change Guard", "Non-Negotiables", and "GitHub Review Threads" sections of …

    line 37
  6. Very specific:

    When review-pr falls back to review-self, follow the canonical single-round override and leave reviewer requests, thread handling, and …

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

OpenIAP Workflows (Claude Code)

The canonical workflow definitions live in .claude/commands/*.md and the shared operating rules live in .codex/skills/openiap-workflows/SKILL.md. Follow both; this file only adds the Claude Code specifics.

Command Mapping

When the user asks in natural language, execute the matching workflow by reading the command file (or invoke the slash command directly when available):

  • Review PR comments / fix review feedback → .claude/commands/review-pr.md (/review-pr), including its single-round Codex fallback when CodeRabbit cannot review the current head, and its .claude/skills/review-self/SKILL.md fallback when Codex is unavailable too; do not invoke other review bots, and remove temporary CodeRabbit trigger and terminal skip/unavailable top-level comments when the loop is clean
  • Audit code against knowledge rules → .claude/commands/audit-code.md (/audit-code)
  • Audit supply-chain security / SBOM → .claude/commands/audit-security.md (/audit-security)
  • Reconcile IAPKit with OpenIAP → .claude/commands/audit-iapkit.md (/audit-iapkit)
  • Compile knowledge / rebuild AI context → .claude/commands/compile-knowledge.md (/compile-knowledge)
  • Resolve a GitHub issue → .claude/commands/resolve-issue.md (/resolve-issue)
  • Verify all / monorepo health check → .claude/commands/verify-all.md (/verify-all)
  • Device-backed E2E regression → .claude/commands/e2e-tests.md (/e2e-tests)
  • Android device-backed E2E regression → .claude/commands/e2e-tests-google.md (/e2e-tests-google)
  • Apple device-backed E2E regression → .claude/commands/e2e-tests-apple.md (/e2e-tests-apple)
  • Stable or RC/next releases → .claude/commands/release.md (/release)
  • Commit, push, or create PR → .claude/commands/commit.md (/commit)

Claude Code Notes

  • Read the "Source Of Truth", "Internal Workflow Change Guard", "Non-Negotiables", and "GitHub Review Threads" sections of .codex/skills/openiap-workflows/SKILL.md and apply them as written; they are agent-agnostic rules, not Codex-only rules.
  • Where that file says to use the Codex Chrome Extension, use Claude's browser tooling (Claude in Chrome / Playwright) instead.
  • Where that file mentions $skill syntax, the equivalent in Claude Code is the matching skill in .claude/skills/ or the slash command in .claude/commands/.
  • When review-pr falls back to review-self, follow the canonical single-round override and leave reviewer requests, thread handling, and polling ownership with review-pr.

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.

Check your setup, free