Qiita CLI × Claude Code — Automating Article Management with Trend Analysis, SEO, and Scheduled Publishing

Ever opened the Qiita editor for the tenth time that week and thought, “there has to be a better way to live”?

That was me. Every Qiita article meant editing in the browser. No Git management, no diffs, manual SEO every single time.

So I built it — a system with Qiita CLI + Claude Code + GitHub Actions that automates article management from creation through publication.

This article walks the full road, including the duplicate article ID trap I fell into and data-driven publishing time optimization.

3 Problems to Solve

Problem	Details
Browser editing every time	Writing in Qiita’s editor → no Git, no diffs
Ad-hoc SEO	Manually fiddling titles and tags each time
Can’t sustain daily posting	Want to batch-write but stagger publication

System Overview

① Share draft with Claude Code
   ↓
② /improve-article skill auto-executes
   ├── Qiita trend analysis (fetches latest each time)
   ├── SEO 6-point check
   └── Auto-calculate scheduled date
   ↓
③ Git managed (daily branch → PR → merge to main)
   ↓
④ GitHub Actions auto-executes
   ├── On main merge → publish immediately → ID commit-back
   └── Daily 20:00 JST → publish 1 scheduled article

Step 1: Managing Articles with Qiita CLI

Qiita CLI is Qiita’s official command-line tool.

npm install @qiita/qiita-cli --save-dev
npx qiita init && npx qiita login && npx qiita pull

This syncs all your Qiita articles as Markdown files in public/. My account had 213 articles pulled in one shot. Slightly emotional moment.

Step 2: Automating Article Improvement with Claude Code

The .claude/skills/improve-article.md skill defines the full improvement process. Telling Claude Code “improve this article” triggers a 10-step automated improvement — including accumulative trend analysis that builds a pattern library over time, rather than overwriting it.

Step 3: Scheduled Publishing — 1 Article per Day

Just specify the scheduled date in frontmatter:

ignorePublish: true                    # Reserved state
scheduled_publish_date: "2026-04-15"   # Auto-publishes on this date

A GitHub Actions cron job runs at 20:00 JST daily and publishes 1 scheduled article. The next date is auto-calculated from the latest existing scheduled date — no mental date math required.

Why 20:00 JST

Time Slot	Effect
Morning (9:00-12:00)	Gets initial traction (work-time searches)
Evening (20:00-22:00)	Read deeply (post-work reading)
Weekends	PV drops to 1/5 of weekdays

Wednesday has the highest Qiita PV in the data, so when I batch-write multiple articles, the most viral candidate gets the Wednesday slot.

Step 4: The Article ID Trap — The Same Article Published 4 Times

Honestly, this one stung.

When Qiita CLI creates a new article, the frontmatter id is null. When merged to main, publish.yml runs qiita publish --all. Qiita CLI treats id: null articles as new articles every time.

The default workflow had no mechanism to commit the Qiita-assigned ID back to the repository.

1st merge → publish id:null article → Qiita assigns ID
          → but repo still has id:null
2nd merge → still id:null → published again as new...

Result: the same article was published 4 times. Then deleting the duplicates on Qiita left files with deleted IDs locally — which threw 404 errors that broke the entire workflow.

The Fix: ID Commit-Back

- name: Commit updated article IDs
  run: |
    git config user.name "github-actions[bot]"
    git config user.email "github-actions[bot]@users.noreply.github.com"
    if ! git diff --quiet public/; then
      git add public/
      git commit -m "chore: update article IDs after publish"
      git push
    fi

Lesson	Details
`id: null` + `ignorePublish: false` is dangerous	Publishes as new on every merge
ID commit-back is essential	Qiita CLI doesn’t persist IDs to the repo by default
Test systems with 1 article first	Validate before any bulk operation

Step 5: Git Workflow — Daily Branch Automation

Claude Code Hooks automate the daily branch dance.

SessionStart Hook: Detects previous day branches → commits & pushes uncommitted changes → auto-creates PRs → deletes merged branches → creates today’s branch.

Stop Hook: Runs secret scan → auto-commits changes → SEO check. No manual commits needed.

Before / After

Aspect	Before	After
Editing	Qiita browser editor	Local Markdown + Git
SEO	Manual each time	Skill auto-optimizes + Stop Hook checks
Timing	Publish immediately	20:00 JST scheduled (Wednesday strategy)
Article IDs	Manual (duplicate risk)	Auto commit-back after publish

In Closing

Building this system, I fell into the “article ID duplicate” trap. But baking that failure into the system itself means I can now run scheduled publishing without second-guessing every merge.

If you’re still editing in the browser, you might pick just one piece of this — even the cron alone — and try grafting it onto your own workflow.

“The Testing Phase Disappeared” — AI-Driven vs Traditional Development Compared — Building an app in 3 weeks with AI
“Black Box Thinking” — Life Is Too Short to Experience Every Failure Yourself — Systematizing failure
“Essentialism” and “Effortless” — The Two Wheels of What to Do and How to Do It — The philosophy of systematization