specrails-core 5.5.1 → 6.0.0

package/templates/commands/specrails/propose-spec.md

@@ -1,102 +0,0 @@
----
-description: Explore a spec idea and produce a structured proposal
----
-
-You are a senior product engineer helping evaluate and structure a spec proposal for this codebase.
-
-The user's raw idea is:
-
-$ARGUMENTS
-
-## Your Task
-
-Before proposing anything, explore the codebase to understand:
-1. What already exists that relates to this idea
-2. What the current architecture looks like in the relevant area
-3. What constraints or patterns you must respect
-
-Use Read, Glob, and Grep to explore. Take at least 3 codebase reads before writing the proposal.
-
-## Required Output
-
-Output ONLY the following structured markdown. Do not add any preamble or explanation outside these sections.
-
-## Spec Title
-[A concise, action-oriented title, e.g., "Add Real-Time Cost Alerts"]
-
-## Problem Statement
-[2-3 sentences: what problem does this solve? Who experiences it? What is the current workaround?]
-
-## Proposed Solution
-[3-5 sentences: what exactly will be built? Be specific about the UI, API, and data changes.]
-
-## Out of Scope
-[Bullet list of things this proposal deliberately does NOT cover]
-
-## Acceptance Criteria
-[Numbered list of testable outcomes. Each criterion must be independently verifiable.]
-
-## Technical Considerations
-[Bullet list of implementation notes, constraints from the existing architecture, risks, and dependencies]
-
-## Estimated Complexity
-[One of: Low (< 1 day) / Medium (1-3 days) / High (3-7 days) / Very High (> 1 week)]
-[One sentence justifying the estimate]
-
----
-
-## Backlog Sync
-
-After generating the proposal, read `.specrails/backlog-config.json` to determine `BACKLOG_PROVIDER` and `BACKLOG_WRITE`.
-
-If `.specrails/backlog-config.json` does not exist, default to `provider=local` and `write_access=true`. Initialize `.specrails/local-tickets.json` if it does not exist (empty store with `schema_version: "1.0"`, `revision: 0`, `next_id: 1`, `tickets: {}`).
-
-### If provider=local — Create Local Ticket
-
-Create a local ticket from the proposal output:
-
-```
-{{BACKLOG_CREATE_CMD}}
-```
-
-Set the following fields:
-- `title`: The Spec Title from the proposal
-- `description`: The full structured proposal markdown (all sections from Problem Statement through Estimated Complexity)
-- `status`: `"todo"`
-- `priority`: Map Estimated Complexity — Low → `"low"`, Medium → `"medium"`, High/Very High → `"high"`
-- `labels`: `["spec-proposal"]`
-- `source`: `"propose-spec"`
-- `created_by`: `"sr-architect"`
-
-Print: `Created local ticket #{id}: {title}`
-
-### If provider=github and BACKLOG_WRITE=true — Create GitHub Issue
-
-```bash
-{{BACKLOG_CREATE_CMD}}
-```
-
-Create a GitHub Issue with:
-- Title: The Spec Title
-- Body: Full structured proposal markdown
-- Labels: `spec-proposal`
-
-Print: `Created GitHub Issue #{number}: {title}`
-
-### If provider=jira and BACKLOG_WRITE=true — Create JIRA Story
-
-Create a JIRA Story using the same authentication and API pattern as `/specrails:auto-propose-backlog-specs`:
-- Summary: The Spec Title
-- Description: Full structured proposal in Atlassian Document Format
-- Labels: `spec-proposal`
-
-Print: `Created JIRA ticket {key}: {title}`
-
-### If BACKLOG_WRITE=false or provider=none
-
-Do NOT create any tickets. Print:
-```
-Spec proposal ready. Create a ticket manually if desired:
-  Title: {Spec Title}
-  Complexity: {Estimated Complexity}
-```

package/templates/commands/specrails/refactor-recommender.md

@@ -1,169 +0,0 @@
----
-name: "Refactor Recommender"
-description: "Scan the codebase for refactoring opportunities ranked by impact/effort ratio. Analyzes code for duplicates, long functions, large files, dead code, outdated patterns, and complex logic. Optionally creates GitHub Issues for tracking."
-category: Workflow
-tags: [workflow, refactoring, code-quality, tech-debt]
----
-
-Scan the codebase for refactoring opportunities, score each by impact/effort ratio, and optionally create GitHub Issues for the top findings in {{BACKLOG_PROVIDER_NAME}}.
-
-**Input:** `$ARGUMENTS` — optional: comma-separated paths to scope the analysis. Flags: `--dry-run` (print findings without creating issues).
-
----
-
-## Phase 0: Pre-flight
-
-Check whether the GitHub CLI is available:
-
-```bash
-{{BACKLOG_PREFLIGHT}}
-```
-
-Set `GH_AVAILABLE=true` if the command succeeds, `GH_AVAILABLE=false` otherwise. Do not stop — analysis proceeds regardless. Parse `--dry-run` from `$ARGUMENTS` and set `DRY_RUN=true` if present.
-
----
-
-## Phase 1: Scope
-
-Parse paths from `$ARGUMENTS` after stripping any flags. If no paths are provided, scan the entire repository.
-
-Always exclude the following from all analysis:
-
-- `node_modules/`
-- `.git/`
-- `.claude/`
-- `vendor/`
-- `dist/`
-- `build/`
-
----
-
-## Phase 2: Analysis
-
-Analyze the scoped files across six categories. For each finding record:
-
-- **file** — relative path
-- **line_range** — start and end line numbers
-- **current_snippet** — the problematic code as-is
-- **proposed_snippet** — concrete refactored version
-- **rationale** — one sentence explaining the improvement
-
-### Duplicate Code
-
-Find code blocks larger than 10 lines that are substantially similar across two or more files. Consolidation into a shared function or module is the expected refactoring.
-
-### Long Functions
-
-Find functions or methods exceeding 50 lines. Extraction into smaller, single-purpose functions is the expected refactoring.
-
-### Large Files
-
-Find files exceeding 300 lines. Splitting into cohesive modules is the expected refactoring.
-
-### Dead Code
-
-Find unused exports, unreferenced functions, and commented-out blocks that have not been active for the lifetime of the file. Deletion or archival is the expected refactoring.
-
-### Outdated Patterns
-
-Find deprecated APIs and old language syntax: `var` instead of `let`/`const`, callbacks instead of `async`/`await`, legacy framework APIs with documented replacements, etc. Modernisation to current idioms is the expected refactoring.
-
-### Complex Logic
-
-Find deeply nested conditionals (more than 3 levels) and functions with high cyclomatic complexity. Extraction, early-return guards, or strategy patterns are the expected refactoring.
-
----
-
-## Phase 3: Score and Rank
-
-Score every finding on two dimensions (1–5 each):
-
-- **Impact** — how much the refactoring improves code quality, readability, or maintainability
-- **Effort** — how hard the refactoring is to implement (1 = trivial, 5 = major)
-
-**Composite score**: `impact * 2 + (6 - effort)`. Higher is better.
-
-Sort all findings by composite score descending. If the same code block was flagged by multiple categories, keep only the highest-scored entry and discard the duplicates.
-
----
-
-## Phase 4: Create GitHub Issues
-
-Skip this phase if `GH_AVAILABLE=false` or `DRY_RUN=true`.
-
-First ensure the tracking labels exist:
-
-```bash
-gh label create "refactor-opportunity" --color "B60205" --force
-```
-
-Fetch existing open issues that already carry the label to avoid duplicates:
-
-```bash
-gh issue list --label "refactor-opportunity" --state open --limit 100 --json number,title
-```
-
-For each of the **top 5** findings (by composite score) that does not already have a matching open issue, create a GitHub Issue with the following body:
-
-```
-## Refactoring Opportunity: {description}
-
-**Category**: {category}
-**File**: {file}:{line_range}
-**Impact**: {impact}/5 | **Effort**: {effort}/5 | **Score**: {composite}
-
-### Current Code
-```{lang}
-{current_snippet}
-```
-
-### Proposed Refactoring
-```{lang}
-{proposed_snippet}
-```
-
-### Rationale
-{rationale}
-
----
-_Generated by `/specrails:refactor-recommender` in {{PROJECT_NAME}}_
-```
-
----
-
-## Phase 5: Output Summary
-
-Print the following report:
-
-```
-## Refactoring Opportunities — {{PROJECT_NAME}}
-
-{N} opportunities found | Sorted by composite score
-
-| # | Category | File | Impact | Effort | Score | Description |
-|---|----------|------|--------|--------|-------|-------------|
-| 1 | {category} | {file}:{line_range} | {impact}/5 | {effort}/5 | {composite} | {description} |
-...
-
-### Top 3 Detailed Recommendations
-
-#### 1. {description}
-**File**: {file}:{line_range}
-**Category**: {category} | **Score**: {composite}
-
-**Current:**
-```{lang}
-{current_snippet}
-```
-
-**Proposed:**
-```{lang}
-{proposed_snippet}
-```
-
-**Rationale:** {rationale}
-
-(repeat for #2 and #3)
-
-Issues created: {N}  (or "dry-run: no issues created")
-```