SidCorp-co
OrganizationSelf-hosted lifecycle platform for software powered by Claude Code. Configurable pipelines, devices you control, no credentials on the server. Apache-2.0.
Categories
Indexed Skills (19)
forge-plan
Write implementation plans for confirmed Forge issues. Use this skill whenever an issue needs a plan before coding begins — exploring the codebase, identifying affected files, and writing step-by-step implementation instructions into the issue's plan field. Triggers on: /forge-plan, planning issues, writing implementation plans, exploring codebase for an issue, preparing issues for development, moving issues from confirmed to approved. Also use when the pipeline needs to advance an issue from confirmed status.
forge-triage
Triage and validate Forge project management issues before development begins. Use this skill whenever issues need to be reviewed for completeness, classified by complexity, or assigned category/priority. Triggers on: /forge-triage, triaging issues, validating issue quality, classifying issue complexity, setting issue priority, reviewing new issues, checking if issues are actionable. Also use when the pipeline needs to move an issue from open to confirmed status. Even if the user just says 'triage this' or 'check if this issue is ready', use this skill.
forge-code
Implement code changes for Forge issues. Use this skill whenever approved issues need to be coded — creates branch, follows the plan, implements changes, builds, reviews, commits, and pushes. Triggers on: /forge-code, coding issues, implementing approved issues, writing code for an issue, building features from a plan. Also use when the pipeline needs to move an issue from approved to deploying.
forge-release
Merge approved issue code to production branch and trigger deployment. Use this skill when an issue has been approved at staging and needs to be released — squash-merges the ISS-* feature branch to the production branch, triggers Coolify deploy, and closes the issue. Triggers on: /forge-release, releasing an issue, merging to production, deploying to production. Also use when the pipeline needs to move an issue from released to closed.
forge-clarify
Clarify and validate Forge issues before planning — reproduce bugs via browser, verify UX expectations for features, capture evidence screenshots. Use this skill after triage (confirmed status) to ensure the issue is well-understood before writing an implementation plan. Triggers on: /forge-clarify, clarifying issues, reproducing bugs, validating UX, verifying issue understanding. Also use when the pipeline needs to move an issue from confirmed to clarified status.
forge-fix
Fix rejected Forge issues based on review or QA feedback. Use this skill when an issue has been reopened with rejection comments — reads the feedback, applies a scoped fix, builds, re-tests, and pushes. Triggers on: /forge-fix, fixing rejected issues, addressing review feedback, fixing QA failures, resolving reopen comments, fixing CI build failures. Also use when the pipeline needs to move an issue from reopen back to deploying.
forge-review
Review code changes for Forge issues. Use this skill for independent code review with fresh context — checks diff against project conventions, finds bugs, security issues, and consistency problems. Triggers on: /forge-review, reviewing code, checking a diff, code review for an issue, reviewing PR changes. Used as a subagent by forge-code during the build+review step (before push), or standalone for manual review.
forge-staging
Merge feature branch to baseBranch for staging deployment. Triggered when an issue reaches pass status — merges the ISS-* branch to the project's baseBranch and sets status to staging. Triggers on: /forge-staging, merging to staging, promoting to staging, deploying to staging. Also use when the pipeline needs to move an issue from pass to staging.
forge-test
QA test Forge issue changes against preview deployments. Use this skill to test like a human QA — hitting the preview backend API and navigating the preview frontend to verify acceptance criteria are met. Triggers on: /forge-test, testing an issue, QA testing, verifying changes on preview, checking if acceptance criteria pass. Also use when the pipeline needs to verify changes at testing status.
forge-design
Use this skill to generate well-branded interfaces and assets for Forge, either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
shop-preflight
Forge⇄Epodsystem integration guide — the thin Forge-owned layer that sits ON TOP of Epodsystem's live single-source playbooks. Defers build mechanics to the live shop-core-rules, holds Forge's durable invariants (build-on-draft, backup-before-publish, verify-via-live-URL), and records how Forge routes around current service quirks so a quirk degrades instead of hard-failing. Referenced by shop-customize-draft, shop-products, shop-menus, shop-verify-draft, shop-publish, shop-rollback. Triggers on: any Epodsystem theme/store mutation, 'customize storefront', 'edit theme', 'add products', 'change menu'.
shop-brief
Triage an Epodsystem storefront issue: read the brief, pull store context, and inventory the current theme/products/menus so planning starts from real state. Use at the triage stage of a website-kind project. Triggers on: storefront/website issues, 'redesign the shop', 'add products', 'new landing page', 'change palette'.
shop-customize-draft
Build Epodsystem storefront changes on the DRAFT theme — sections, layout, palette, typography — via the shop MCP tools. Use at the code stage of a website-kind project. Triggers on: implementing a storefront redesign, editing theme sections, applying a palette, customize_theme.
shop-design-spec
Clarify an Epodsystem storefront issue into a concrete design spec (sections, products, menus, palette) and confirm the draft-theme build target before coding. Use at the clarify stage of a website-kind project. Triggers on: storefront design clarification, 'what should the page look like', verifying a redesign brief.
shop-menus
Edit Epodsystem store navigation menus reliably, working around the stale-storeMenu read bug (always re-query after mutating). Use at the code stage of a website-kind project. Triggers on: 'change the menu', adding/removing nav items, reordering navigation.
shop-products
Add or update Epodsystem products and collections so they render correctly in grids and cards (EAV images + reindex, smart-collection rules, visibility). Use at the code stage of an ecommerce website-kind project. Triggers on: 'add N products', updating a collection, fixing products that don't show in a grid.
shop-publish
Publish an Epodsystem storefront: snapshot the current live theme as a rollback backup, promote the verified DRAFT theme to main (live), clear the storefront cache, and confirm the live URL reflects the change. Use at the release stage of a website-kind project after shop-verify-draft passes. Triggers on: 'publish the storefront', 'go live', promote draft to main, release a theme change.
shop-rollback
Roll back an Epodsystem storefront after a bad publish by re-publishing the independent backup theme that shop-publish retained (NOT by re-activating the old main id — publishing can destroy it). Use at the fix stage of a website-kind project, or invoked by shop-publish on a failed live check. Triggers on: 'roll back the storefront', 'revert the theme', publish broke the live site.
shop-verify-draft
Verify Epodsystem storefront changes on the draft theme — load the live/draft URL, assert sections render, links return 200, products/menus bind real data — and FAIL the stage on mismatch. Use at the test stage of a website-kind project. Triggers on: verifying a storefront change, QA of a theme draft, checking a redesign.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.