refactor: Forgejo-only task suite; drop taskpy #10
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
public/chiche-plugins!10
Loading…
Reference in a new issue
No description provided.
Delete branch "refactor/fj-only"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal: Make these skills specific to the homelab Forgejo setup -- one task suite, Forgejo-only, with no skill or reference file over 500 lines.
Value: med
Effort: half-day
Why
Every repo here is on Forgejo (
fj), so the cross-forge machinery (GitHubgh/ Forgejo detection + paired command branches) in the task suites was dead weight. Thetaskpysuite was a verbose near-duplicate oftask-- which is already language-agnostic (it reads a## Toolchainblock from CLAUDE.md/AGENTS.md). Consolidated to one Forgejo-onlytasksuite, moved the genuinely Python-specific bits into a per-language reference, capped every file at 500 lines, and -- per review feedback -- name the forgejo-cli skill once per file with intent-based steps.Steps
taskpyplugin; fold Python specifics intotask-implement/languages/python.md(per-language reference; other languages get a sibling file). Point the marketplace registry + README attask.taskskills to the per-language reference (the Toolchain-scaffold step in task-implement).tasksuite Forgejo-only: remove forge-detection, theghcommand branches, GitHub-only concepts (--draft,gh auth, the GitLab/Bitbucket "manual" fallbacks), and theforge/forge_clifields. Files: task-new, task-implement (SKILL + flow + worktree-and-branches), task-orchestrate (SKILL + test-fix-loop), task-review.forgejo-cliskill once per file; the steps express intent (notfjcommands), including auth.gh apiaside inforgejo-cli/agents/fj-worker.md.taskplugin.json + registry descriptions to Forgejo-only.gh/ GitHub anywhere.Notes
Review-driven refinements (from the inline PR comments):
python.mdpoints at the repo's own config (pyproject.toml / README / CLAUDE.md) instead of prescribing a package manager or commands; theforgejo-cliskill is named once per skill with intent-based steps rather than on every operation;fjauth is folded into "the forgejo-cli skill owns thefjmechanics (including auth)."Out of scope: no
gh_write.py(GitHub dropped entirely); no test framework (matches repo posture).b306e0da998fa1da238d@ -392,3 +330,1 @@write the appended body to a tmp file and edit it with `fj_write.pyissue-body <umbrella> --body-file <path>`). Don't duplicate a row thatalready lists this slug (resuming).<PR title>` to `## Linked PRs`, write it back: invoke the `forgejo-cli`forgejo cli is mentioned toooo many times in this file, just mention the skill once, it should not be needed this many times, just call the skill in an agent with what you want to do, and the rest should come from the skill
WIP: refactor: Forgejo-only task suite; drop taskpyto refactor: Forgejo-only task suite; drop taskpyForgejo-only refactor complete and marked ready.
taskpyplugin; onetasksuite remains. Python specifics moved totask-implement/languages/python.md-- a per-language reference that points at the repo's own pyproject / README / CLAUDE.md rather than prescribing a package manager or commands.tasksuite is Forgejo-only: nogh, no forge-detection, no--draft/forge_cli/ manual fallbacks.forgejo-cliskill is named once per file; every step expresses intent (including auth), notfjcommands.Verified clean: no
gh/ GitHub anywhere, marketplace + plugin JSON valid. Ready for review + merge.