Coding standards, frameworks, refactoring, and code review (16.9K skills)
Save working changes as local Git commits with messages that explain the outcome. Follow the project's commit style, select files explicitly, and split clearly separate changes into a few logical commits when appropriate.
Address existing feedback on a GitHub pull request, a proposed code change. Evaluate comments against the code, apply valid fixes, and verify replies and thread resolution, with options for local handoff or resuming saved work.
Carry a request through the appropriate Compound Engineering skills with minimal intervention. For code changes, the workflow covers planning, implementation, review, browser testing, and an open pull request with automated check results assessed.
Review code changes or a pull request for bugs, effects on existing behavior, test gaps, and project standards. Receive findings supported by the code and a clear account of review coverage, with local fixes available when explicitly requested.
Turn a vague feature idea into clear requirements through dialogue. Define what to build, its scope, and success criteria, then capture the result in a short chat summary or a requirements document ready for implementation planning.
Check the Compound Engineering environment and repository settings, identify configuration issues, and report optional tools. Confirm where generated documents will be stored, make approved configuration fixes, or scaffold a Compound Pack with pack:<id>.
Set up a separate Git working directory for a new task or an existing branch, pull request, or commit. Detect and reuse existing isolation, prefer the agent environment's worktree tools, and report the working path and branch.
Commit and push code changes, then open a pull request with a clear title and description. You can also draft or update PR descriptions and hand published requests to the follow-up monitoring workflow.
Review Pascal pull requests or branches against documented architecture rules. Check package responsibilities, node extension patterns, state management, and rendering subscriptions to identify misplaced code, compatibility breaks, and changes that could cause excessive redraws.
Create or update a pull request from the current branch using its actual commits and changes. Fill the repository template with a concrete description, reviewer test steps, and accurately reported checks, then push the branch.
Review a pull request, a proposed code change, for code that can be removed or simplified. Consider product decisions, final functionality, and whether rare edge cases have led to unnecessary complexity.
Prepare a development branch for final maintainer review by checking security, unnecessary complexity, and billing abuse risks. Fix confirmed issues, run local checks and tests, then push changes and create or update the pull request.
Turn rough bug reports, feature requests, support notes, or pull requests into concise issues. Explain the current problem and desired behavior in plain language, preserving useful evidence without prescribing how developers should implement a solution.
Prepare an OpenSEO release by updating the version, selecting user-visible changes from commits, and writing concise release notes. Review agents check the draft against the code before a pull request is opened for the release.
Create a concise review brief for a branch or pull request. Show critical code, before-and-after behavior, risks, test status, and commands to try the change, helping maintainers focus their review on consequential decisions.
Record recurring setup and workflow problems that a repository can fix, so future contributors can avoid the same friction. Also review existing entries, remove duplicates, prioritize useful fixes, and preserve a history of resolved problems.
Create or update skills using OpenSEO's repository conventions. Keep one canonical source, distinguish internal and public workflows, maintain Claude Code links, and register public skills in documentation, the in-app agent, and plugin bundles.
Set up and run Happy components locally, including its CLI, server, mobile app, and desktop app. The guide covers building, testing, checking logs, and separating development data using pnpm, the project's package management tool.
Trace application behavior and explain data structures using compact text tree diagrams. The diagrams connect user actions to real functions, data types, state changes, and the components that render again as a result.
Organize Happy's GitHub issues, find duplicates, and check whether reported bugs are fixed on main, the primary development branch. Prepare replies and proposed actions for maintainer review, with explicit approval required before changes affecting contributors.
Search past coding sessions across Claude Code, Codex, and Cursor to recover earlier attempts, failed approaches, decisions, and findings. It filters history by topic and time, then summarizes technical details relevant to the question.
Attach screenshots, images, or videos to GitHub pull requests and issues using GitHub CLI. It also covers embedding images within comment text, adding alternative text, and retrieving an uploaded asset’s URL from the posted comment.
Review code changes for compatibility between a desktop app and den, its cloud API. It flags changes that could break published apps, identifies desktop features depending on unavailable APIs, and explains the required rollout order.
Manage OpenWork feature releases with feature flags, switches that control access to new behavior. Register features before coding, release them by organization and deployment, prepare a global shutdown option, and remove temporary flags after rollout.