morphet81
- 21 skills
- 0 followers
- 6 hours ago last updated
- ▌ Forge · morphet81 bundleImplement a ticket or description. Prefer `scrutiny forge` (fetch mirror, fcli, knobs, TDD plan confirm, single|team implement). Or chain forge-fetch / plan-write / context / brief. Reuses scrutiny probe for post-impl.
- ▌ Parley · morphet81 bundleAddress unresolved GitHub PR review comments. Prefer `scrutiny parley` (fetch threads, knobs, isolated|team fix agents, optional evangelist verify, host commit/push, script thread replies). Or chain parley-fetch / plan-write / reply.
- ▌ Scrutiny · morphet81 bundleProbe skill (code review). Prefer `scrutiny probe` for script-orchestrated runs (headless agents, isolated|team spawn). Or chain Rust eval → map → pack → scan, plan-confirm, optional Task agents, probe-session-write, findings triage, post-comments. Local default; PR URL/number for PR mode.
- ▌ Adb · morphet81Use ADB to interact with an Android device or emulator. Takes a screenshot, understands the screen, performs actions (tap, swipe, type, navigate), and loops until the mission is complete.
- ▌ Team · morphet81Set up a multi-agent team to implement a new functionality. Spawns a product owner, optional designers, developers, and testers based on the task. Provide a description of what to build.
- ▌ Cleanup · morphet81Review uncommitted changes, verify tests, fix lint and audit issues, ensure 100% coverage, then propose fixes for approval before committing.
- ▌ Localise · morphet81Generate an HTML translation helper page for Lokalise. Use when the user provides English text (singular/plural) and wants translations across all 23 supported languages, rendered as an interactive HTML page with copy buttons. Triggers on phrases like "translate for Lokalise", "generate translations", "translation table", or when the user provides English strings and mentions languages/i18n/localization.
- ▌ Pre Push · morphet81Run pre-push checks including tests and linting to ensure code is clean and ready to push. Automatically detects project type and available scripts. Runs independent checks in parallel using agents.
- ▌ Create Pr · morphet81Push the current branch and create a pull request on GitHub. Derives the title and description from any JIRA ticket referenced by the branch, and references every issue (JIRA, GitHub, etc.) the PR actually fixes — never related items. Draft by default, use --no-draft for a ready PR.
- ▌ Screenshots · morphet81Take screenshots of components affected by recent changes, from the running app or Storybook. Supports custom instructions for pages to visit and actions to perform. App screenshots are captured via temporary e2e tests.
- ▌ Setup Branch · morphet81Create a new branch and worktree from a JIRA ID or URL. Determines branch prefix (fix/ or feat/) from the JIRA item type, sets up the worktree one level up, and installs dependencies.
- ▌ Translate PDF · morphet81 bundleTranslate a PDF document from one language to another. Extracts text to structured Markdown, translates it, and builds a new translated PDF. Requires a Python environment with pymupdf, markdown, and weasyprint.
- ▌ Address Ticket · morphet81End-to-end ticket implementation with a multi-agent team using TDD. Retrieves JIRA ticket details and Figma designs, spawns a PO to write requirements, gets developer approval, then proposes a test plan for review. Once tests are approved, implements tests first (red), then production code to pass them (green). Use --no-jira to skip JIRA retrieval and use inline instructions instead. Use --headless for fully autonomous execution where a reviewer agent replaces human approval.
- ▌ Release Review · morphet81Compare two git tags or commits and analyze all changes for deployment readiness. Produces two separate reports — one for manual QA (no code details) and one for developers (technical details with code where needed).
- ▌ Review Changes · morphet81Review code changes with a small team — two senior engineers review independently, debate their findings, then a team lead reports a consolidated list. Local mode compares the current branch against a base branch; PR mode (auto-enabled when a PR URL or number is supplied) offers to post the findings as PR review comments. PR mode is strictly read-only — no file in the working tree is ever modified, and every developer instruction is interpreted as an update to the comments plan. The agent never checks out a branch in the current working directory; if it needs files at another ref, it creates a temporary worktree and removes it before presenting the report. Local mode lets the developer pick findings to fix, and the same two engineers implement them in auto mode. Engineers read the project's AI documentation (architecture first) before reviewing, and explicitly check for reuse violations and unused established practices.
- ▌ Merge Base Branch · morphet81Select base branch (from .agent, git history, or main), fetch, stop if already up to date, commit all WIP, merge, resolve conflicts, then lint, tests at 100% coverage, and build—with commits after each fix phase.
- ▌ Verify Test Cases · morphet81Verify test cases in all test files modified since branching out from base branch. Checks that test cases make sense, have no duplications, and provide meaningful coverage. Spawns parallel agents for multi-file analysis. After the user confirms test-case changes, runs coverage (npm test:coverage or Jest/Vitest fallback) and fixes tests until coverage passes.
- ▌ Create Jira Ticket · morphet81Create a JIRA ticket from user instructions via acli. Uses project from the current branch when possible, lists project epics, recommends the best epic, asks confirmation before creating, uses ADF descriptions, and can attach Figma designs via the Jira integration.
- ▌ Update Jira Ticket · morphet81Compare the JIRA ticket description to changes made in the current branch and propose description edits and/or comments to keep the ticket accurate and well-documented.
- ▌ Address Pr Comments · morphet81Retrieve unresolved PR review comments and general conversation comments (including actionable notes from the PR author), explain each issue and propose fixes interactively, then spawn a coordinated developer team to implement approved fixes. After committing, respond to each comment on GitHub with resolution details.
- ▌ Address Github Issue · morphet81Retrieve a GitHub issue using the `gh` CLI, analyze it, and spawn a PM + developer team to address it. Accepts an issue URL, issue number, or `owner/repo#number`.