meta-secret

Draft and update PR/MR title and description from full branch scope; use before gh pr create or gh pr edit.

Expected shape of the planning phase output before code-implementer; aligns with write-implementation-plan.

Write or update project skills and rules markdown files (.ai/skills/, .ai/rules/, .cursor/rules/). Use when creating a new SKILL.md or rule, updating an existing one, or when the user asks to document a workflow, pattern, or convention as a reusable skill.

Guard architecture, style, and security in meta-secret core crate changes.

Guard architecture, style, and security in cli/meta-cli changes.

Guard architecture, style, and security in mobile/uniffi library changes.

Guard architecture, style, and security in web-cli/ui changes.

Format a GitHub issue Summary for the feature-planner and later phases after gh issue view.

Preserve project architecture and SOLID when proposing or writing code. Always identify the correct layer and minimal design first.

Explore and shape a new feature before code generation. Always determine architectural placement, design options, trade-offs, and recommended approach first.

Diagnose runtime and launch issues that happen only on physical iPhone devices. Always plan first, then wait for approval before changing code.

Diagnose and repair Kotlin Multiplatform + Swift build failures. Always plan first, wait for confirmation, then apply minimal fixes.

Format a GitHub (or GitLab) issue Summary for the feature-planner and later phases after gh issue view.

Structure a manual feature or bug report before feature-planner when not starting from a GitLab issue.

Checklist for merge request title and description before release-manager creates the MR.

Optional retrospective—suggest 0–2 repo improvements (skill, command, rule, or hook) when triggers fire; otherwise say to change nothing.

Use when addressing human, Codex, or automated PR review comments in Nook. Inspect submitted reviews, inline review threads, and PR comments; build a checklist from actionable items; verify each finding; fix or explain it; validate, push, reply on GitHub, and resolve conversations only after the agent's targeted reply is visible. Never request or wait for external reviews or checks.

Default agent workflow for every coding task in this repository: fetch repo, branch from origin/main, implement, always host-apply task format (and the UI demo contract when UI paths change), commit and push/open the PR, then monitor applicable repository-owned PR checks on GitHub Actions (no required local task check / ci:pr); on failure fix from CI logs, format, and push again until Nook's PR checks are green, resolve every actionable comment already present without waiting for reviewers, then squash merge; afterward publish and analyze the PR statistics in a separate check-free stats-only PR. Always follow this pipeline for implementation work unless the user explicitly asks for a read-only or question-only answer.

Captures user-explained codebase lessons as durable project skills in the canonical .cortex/dynamic-skills registry and applies them to refactors. Use when the user invokes /dynamic-skill, asks to create or update dynamic skills, explains what is wrong with a recurring code pattern, or wants to refactor code using accumulated skill guidance.

Ship Nook PRs efficiently with preflight/readiness audits, format-then-push, GitHub Actions-only product validation, and repository-only event watching without waiting for external review.

Format locally with task format; run every product gate on GitHub Actions. Do not require local task check or ci:pr for merge.

Always host-apply task format and pass the UI demo contract before every Nook PR push. Use when committing, pushing, fixing CI format/demo failures, or when sealed-image Prettier/rustfmt lag would otherwise burn a Verify cycle.

Validate Nook hosted extension origins, identity, archives, redirects, injection exclusions, and isolated browser profiles before release.

Use when Nook work is too large, risky, blocked, out of scope, or deferred. Search existing GitHub issues, preserve team-owned issue metadata, update or create an aggregate issue, create or attach focused sub-issues, and report the issue hierarchy in the handoff.