From 6c6f66a8391ef8679fe3ebf42aca34be579044d1 Mon Sep 17 00:00:00 2001 From: Claude Code Date: Tue, 30 Jun 2026 00:58:15 +0000 Subject: [PATCH 1/2] Trim centralized autonomous-workflow sections from CLAUDE.md Remove the Work Control, Track issues and blockers, and Issue Dependencies sections, now centralized in the find-work skill (claude-autonomous-scheduler plugin) as the single source of truth. --- CLAUDE.md | 20 -------------------- 1 file changed, 20 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index fceba0d..a3c3ab8 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -46,30 +46,10 @@ When planning tasks, provide concrete implementation steps without time estimate - "Implementation involves: parsing new environment variable, updating repository selection logic, and adding tests" - Focus on technical scope and complexity, not duration -## Track issues and blockers - -* When blocked in your development because you're missing some capability (e.g. MCP server or access to a specific development tool in your environment), create an issue in this Github repository to describe what's missing -* The issue title should contain `[Claude]` as a prefix. e.g. `[Claude] Missing tool: ` -* Check beforehand that a similar issue does not exist. If one does exist, consider adding additional context and information based on the current task at hand -* Avoid duplicate content in the Github issue as this will be read by humans. Consider editing existing comments to refine the explanations rather than adding new comments -* Do not apply the `claude` tag to the issue yourself -* Remember to use the same footer as for other discussions to indicate that the issue content or comment was generated by Claude - ## Clean-up changes * When removing logic, don't leave comments about it. If things don't exist, we don't need to mention them -## Work Control - -Only work on issues with the `claude` label and no open dependencies. The `find-work` skill handles task detection and priority routing. - -* NEVER add the `claude` label on a Github issue yourself unless it's requested explicitly -* NEVER work on an issue that depends on functionality added by another open issue - -## Issue Dependencies - -* Never use GitHub's sub-issue/parent-issue feature (addSubIssue/removeSubIssue). Use native blocked-by dependencies exclusively. - ## Skill Creation When creating skills, invoke both `/skill-development` and `/skill-creator` for comprehensive coverage. They provide complementary guidance: `/skill-creator` covers core design principles and conciseness, while `/skill-development` covers writing style rules, trigger descriptions, and validation. From 5ddfa1e7419e5b820753a850e07e3b538bc8bf8f Mon Sep 17 00:00:00 2001 From: Claude Code Date: Tue, 30 Jun 2026 22:50:05 +0000 Subject: [PATCH 2/2] Run Code Analysis on all PRs to unblock doc-only changes The `analysis` workflow is a required status check, but its `paths-ignore` filter skipped it for doc-only changes (**.md, LICENSE, docs/**). A skipped workflow never reports its required context, so any documentation-only PR stayed permanently BLOCKED on a pending `analysis` check. Drop the path filters so `analysis` always runs and always reports, matching the other required check (`check` in go.yml), which has no path filters. --- .github/workflows/analysis.yml | 8 -------- 1 file changed, 8 deletions(-) diff --git a/.github/workflows/analysis.yml b/.github/workflows/analysis.yml index bed79e6..5af9c60 100644 --- a/.github/workflows/analysis.yml +++ b/.github/workflows/analysis.yml @@ -5,16 +5,8 @@ name: Code Analysis on: push: branches: [ "main" ] - paths-ignore: - - '**.md' - - 'LICENSE' - - 'docs/**' pull_request: branches: [ "main" ] - paths-ignore: - - '**.md' - - 'LICENSE' - - 'docs/**' permissions: contents: read