692 skills · sorted by relevance
Organize code changes into focused commits that follow the project's existing message style. Clean up branch history with rebase, resolve conflicts, and investigate when particular code changed or who last modified a line.
Manage Git changes and investigate repository history with evidence from commands. Group related edits into focused commits, reorganize branch history when requested, trace changes, and identify the first faulty commit when a repeatable check is available.
Find unused TypeScript code, verify references with a language server, and assign removals to parallel agents. Group changes by file, create separate commits, and check types, tests, and the build after cleanup.
Transfer selected Chatbox Pro commits into the open source edition using cherry-picking, which copies individual changes. The skill handles excluded files, package names, dependency conflicts, lockfile regeneration, and version tags for manual releases.
Follow Conductor's development plans using test-driven development: write a failing test, implement the change, then improve the code. Manage phase verification, progress updates, and focused git commits as tasks move toward completion.
Prepare repository contributions by checking existing guidelines, related issues, branch naming rules, commit formats, and pull request templates. Organize changes into logical commits and assemble submissions that follow the project's documented contribution process.
Turn recent work or rough notes into a concise daily standup update organized by yesterday, today, and blockers. Connected tools can supply commits, pull requests, ticket changes, and relevant discussions to help assemble the report.
Re-review a GitLab merge request after new commits, track the outcome of every previous finding, and inspect both new changes and the full proposal. Verify the current code, then publish a test report and review verdict.
Re-review a pull request after new commits arrive. Check every previous finding, inspect the new changes for regressions, and review the full current change. Run relevant verification and publish a test report and review verdict within Factory.
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.
Write English pull request titles and descriptions that explain behavior changes, affected areas, verification results, risks, and rollback steps. Attach demo videos or screenshots with gh, the GitHub command-line tool, and keep existing PR text consistent with the final changes.
Turn Git commits, records of code changes, into clear release notes for users. The skill groups updates by type, rewrites technical descriptions in plain language, and filters out internal work such as refactoring and tests.
Investigate Sentry errors by fetching event details and the actions leading up to failures through Composio CLI. Connect error locations to local code, inspect suspect commits, propose patches, run tests, and rank unresolved issues.
Complete small development tasks with a plan, focused commits, and recorded progress. Add discussion, research, or verification when needed, and use task listings and status checks to find and resume unfinished work.
Create a pull request branch from the current branch while excluding .planning/ commits. This keeps planning documents out of the review so reviewers can focus on the code changes.
Turn recent work or rough notes into a concise daily standup update organized by yesterday, today, and blockers. Connected tools can supply commits, pull requests, ticket changes, and relevant discussions to help assemble the report.
Coordinate investigations into regressions introduced by PRs or commits. Assign preparation, discovery, reproduction, independent verification, decisions, and reporting to separate stages, while preserving evidence and progress records for later resumption.
Compare code structure across two commits, tags, or directories to identify security-relevant changes. Produces a report on new attack paths, privilege boundaries, complexity, and how widely a change could affect other functions.
Read staged Git changes and suggest a message in Conventional Commits format, a structured way to describe changes. Include a concise subject and relevant details, then request confirmation before creating the commit.
Create a GitHub pull request from the current branch with a structured title, a clear explanation of behavior changes, and recorded check results. For UI changes, attach before-and-after screenshots so reviewers can assess the visual differences.
Review a branch's commits, combine adjacent changes that belong together, and improve commit messages. A rebuilt history is prepared separately and replaces the original branch only after the user reviews and confirms the proposed changes.
Organize mixed Git changes into focused commits and pull requests that reviewers can follow. It preserves unrelated work, checks proposed changes for private information, runs relevant validation, and pushes or opens pull requests when authorized.
Manage Git changes and investigate repository history with evidence from commands. Group related edits into focused commits, reorganize branch history when requested, trace changes, and identify the first faulty commit when a repeatable check is available.
Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template. Use when asked to write the changelog for this release, what changed since the last tag, draft release notes from my commits, or summarise this range for users in Cowork. Reads commits/PRs between two refs via the GitHub connector, groups them into user-facing changes (features / fixes / breaking), translates commit-speak into human benefit, and produces a changelog artifact ready for the release.
The English summary is being prepared. Showing the original description.