Add OCI Functions skills

[cvvasishta]

Closes #58

Summary

Adds OCI Functions skills under oci/functions/ for local deployment and troubleshooting workflows.

This PR includes:

• oci-functions-deploy: dependency-first local OCI Functions setup, Fn context validation, OCIR auth checks, application selection/creation, function scaffolding, deployment, and explicit mutating-action gates.
• oci-functions-troubleshoot: diagnosis-first workflow for setup/control-plane, application creation, deployment, invocation, observability, limits, and common error patterns.
• OCI domain TOC updates in oci/SKILL.md.
• Root README navigation updates for the OCI domain.
• Public Oracle ## Sources sections on OCI Functions skill and reference markdown files.

What Changed

This PR adds OCI Functions skills under oci/functions/:

• oci/functions/oci-functions-deploy/

  • Guides local macOS/Linux OCI Functions deployment workflows.
  • Validates Fn CLI, OCI CLI, Docker, Fn context, OCI auth, and OCIR registry auth.
  • Supports Java, Python, and Node function scaffolding and deployment.
  • Requires explicit confirmation for mutating actions such as installs, Docker login, Fn context changes, app creation, network creation, fn init, and fn deploy.
  • Includes helper scripts and contract tests for command gating and machine-readable output.

• oci/functions/oci-functions-troubleshoot/

  • Provides a read-only, diagnosis-first triage workflow.
  • Covers setup/control-plane, app creation, deploy, invoke, observability, metrics, limits, and common error patterns.
  • Hands off mutating remediation to $oci-functions-deploy only after diagnosis.

This PR also updates:

• oci/SKILL.md as the OCI domain table of contents.
• README.md to include the current OCI domain layout.
• All OCI Functions markdown files with ## Sources sections backed by public Oracle documentation.

Safety and Public-Readiness

• Customer-facing language only.
• No internal Confluence, Slack, Jira, tenancy-specific, roadmap-only, or unpublished behavior included.
• Mutating actions are explicitly classified and confirmation-gated.
• Public Oracle sources are listed in each skill/reference markdown file.
• OCI CLI, Fn CLI, Docker, and OCIR command forms were checked against installed CLI help and public Oracle documentation.

Platform Scope

The helper scripts in oci-functions-deploy are intended for local macOS/Linux environments. Windows automation is out of scope for this initial contribution. Windows users can still use the skill guidance manually, but the bundled shell scripts are not expected to run natively on Windows without a POSIX-compatible environment.

Note on Fn Project CLI Installer

install_fn_linux.sh uses the Fn Project CLI installer from the public fnproject/cli GitHub repository because Oracle’s public OCI Functions QuickStart documents that URL as the Fn CLI install path. The helper is confirmation-gated and identified as a high-risk remote installer path before execution.

Source:

• Oracle OCI Functions QuickStart on Local Host: https://docs.oracle.com/en-us/iaas/Content/Functions/Tasks/functionsquickstartlocalhost.htm

Validation Performed

• Ran ShellCheck:
  • shellcheck oci/functions/oci-functions-deploy/scripts/*.sh oci/functions/oci-functions-deploy/tests/test_skill_contract.sh
• Ran Bash syntax checks:
  • bash -n across deploy scripts and tests
• Ran contract tests:
  • bash oci/functions/oci-functions-deploy/tests/test_skill_contract.sh
  • Result: 6 passed, 0 failed
• Verified every markdown file under oci/functions has a ## Sources section.
• Verified stale $oci-function-deploy handoff references were corrected to $oci-functions-deploy.
• Updated deprecated VCN create command usage from --cidr-block to --cidr-blocks.

[winnielinnie]

@krisrice Hey Kris, any updates to get this reviewed and merged?

[krisrice]

Thanks for the contribution. I reviewed this against the current repo patterns and I don’t think it’s mergeable as-is yet.

Main items to address:

1. Rebase and reconcile with current main

This PR currently conflicts with README.md and oci/SKILL.md. Since OKE and Enterprise AI have already landed, the OCI domain index needs to route all three areas:

• oci/oke/
• oci/enterprise-ai/
• oci/functions/

Right now the PR rewrites oci/SKILL.md as if OCI Functions is the only populated OCI service area.

2. Fix .gitignore

git diff --check reports trailing whitespace / line-ending issues in .gitignore.

Also, please remove .github from .gitignore unless there is a specific repo-maintainer reason to ignore it. Ignoring .github could hide future workflows, rules, templates, or repo config from Git.

3. Fix the failing test

The included test suite currently fails:

not ok - confirm gate interactive fresh nonce: interactive re-approval should succeed on a second identical command
Passed: 5
Failed: 1

This needs to pass before merge, especially because the PR introduces executable mutation gates.

4. Reconsider the amount of executable automation

This PR adds a large set of .sh files that install tools, configure Fn contexts, create/update OCI resources, manage Docker auth, create networking/apps, scaffold functions, and deploy.

That is much heavier than the repo’s normal “source-backed skill guidance” pattern. Shell scripts are not automatically disallowed, but executable automation in this repo should have a high bar:

• small and easy to audit
• read-only or generate-only by default
• explicit approval gates for every mutation
• no hidden remote execution
• passing tests
• clearly referenced from SKILL.md
• aligned with an agreed repo policy for executable helpers

Please either trim this down to normal skill guidance plus a small number of focused helpers, or confirm with maintainers that this repo should host this level of deployment automation.

5. Clarify nested skill structure

The PR adds multiple nested SKILL.md files:

• oci/functions/oci-functions-deploy/SKILL.md
• oci/functions/oci-functions-troubleshoot/SKILL.md

Nested skills can be reasonable, but oci/SKILL.md should make the routing model explicit and consistent with the rest of the OCI domain. The current branch needs to be updated so Functions fits alongside OKE and Enterprise AI rather than replacing them.

Once those are addressed, I’d re-review the PR.