Skip to content

Instantly share code, notes, and snippets.

View 5ChStereo's full-sized avatar

5ChAGI 5ChStereo

View GitHub Profile
@stevenrouk
stevenrouk / next-task.md
Last active August 14, 2025 04:57
Claude Code commands for starting project documentation (/start-project), executing next tasks (/next-task), and updating documentation when task is complete (/update-task-documentation). Current working version -- last updated 2025-08-02.

Complete the next task from the plan in docs/start-here.md

Please look at docs/start-here.md and follow the instructions. Your job is to get the next task done. Ultimately, you are the one guiding the work and making sure it meets what it's supposed to do. Chunk the work into small pieces, when it's helpful.

First, review the necessary files, think carefully, review more, and then create a plan to create the next chunk of work. Output your plan for approval by me (the user) before proceeding. Pause after outputting the plan to wait for my input.

Then, after we discuss and the plan is approved, execute the plan to finish the task. Use subagents when helpful. Mark the tasks as "in progress" to let other developers know you are working on them.

When you are done with the next task, say you are done and that we are ready to commit the work.

@sinbad
sinbad / backup_gitea.sh
Created August 9, 2020 14:58
My Gitea Backup & Restore Scripts
#!/bin/bash
# `gitea dump` doesn't currently back up LFS data as well, only git repos
# It primarily backs up the SQL DB, and also the config / logs
# We'll backup like this:
# * "gitea dump" to backup the DB and config etc
# * tar / bzip all the repos since they will be skipped
# * Not rotated because git data is immutable (normally) so has all data
# * rsync LFS data directly from /volume/docker/gitea/git/lfs
# * No need for rotation since all files are immutable